← previous blocknext block →recent activity
Analyzing
Block #86,784,508
23 transactions · 21 stateful · 2026-07-10 06:27:13 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,784,508 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w08w19w210w315w116w421w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x71658d1a…f1ec
0x34b655…2a6f
6 touches
3 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x3a2358d3…f072
0x34b655…2a6f
4 touches
1 conflict
0x516ec46d…fc46
0x34b655…2a6f
4 touches
1 conflict
0x6b8d576d…e61e
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xada5ad75…1d24
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity