← previous blocknext block →recent activity
Analyzing
Block #86,830,646
13 transactions · 11 stateful · 2026-07-10 11:35:41 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,830,646 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd95edc7f…db92
0x34b655…2a6f
4 touches
1 conflict
0xf464e900…f28c
0x34b655…2a6f
4 touches
1 conflict
0xf464e900…f28d
0x34b655…2a6f
4 touches
1 conflict
0x15b254ac…664f
0x34b655…2a6f
4 touches
1 conflict
0x251978e2…79e8
0x34b655…2a6f
4 touches
1 conflict
0x5befdf42…39bf
0x34b655…2a6f
4 touches
1 conflict
0x7e8ebc95…aded
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity