← previous blocknext block →recent activity
Analyzing
Block #86,363,829
16 transactions · 12 stateful · 2026-07-08 07:33:31 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,363,829 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w19w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dc93134…aaef
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x18fd08e2…ee6f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x25cdc19f…7efa
0x34b655…2a6f
4 touches
1 conflict
0x2ff23f56…d367
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 0x5dc9313484…1faaef
Audit this contract →
← previous block·next block →recent activity