← previous blocknext block →recent activity
Analyzing
Block #86,257,092
8 transactions · 7 stateful · 2026-07-07 19:41:03 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,257,092 · 8 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
1w03w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0xec0fe5af…ad82
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0xbf140d9d…4923
0x34b655…2a6f
3 touches
1 conflict
0x6db97e95…8353
0x34b655…2a6f
3 touches
1 conflict
0x3823a559…aaa7
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
3 conflicts on slot 0xe945224145…7195a3
Audit this contract →
← previous block·next block →recent activity