← previous blocknext block →recent activity
Analyzing
Block #86,628,982
17 transactions · 13 stateful · 2026-07-09 13:07:17 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,628,982 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x14a1db40…b213
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeed13780…75e7
0x34b655…2a6f
3 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
2 touches
0 conflicts
0xfaef08b1…0696
0x34b655…2a6f
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xe06bbb2ef5…889416
Audit this contract →
← previous block·next block →recent activity