← previous blocknext block →recent activity
Analyzing
Block #86,217,309
19 transactions · 16 stateful · 2026-07-07 15:15:16 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,217,309 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w19w213w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6b0ceba5…f462
0x34b655…2a6f
4 touches
1 conflict
0x7618d94e…2ec3
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
0x267fe70d…159e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
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 0x4efae87285…886aa8
Audit this contract →
← previous block·next block →recent activity