← previous blocknext block →recent activity
Analyzing
Block #86,922,737
9 transactions · 7 stateful · 2026-07-10 21:51:22 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,922,737 · 9 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
1w02w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bf44783…6166
0x34b655…2a6f
8 touches
6 conflicts
0xc8e73a7c…8228
0x34b655…2a6f
6 touches
3 conflicts
0xc994d804…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xc994d804…2fcb
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7babfe9a…ff96
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 0x5bf4478367…f06166
Audit this contract →
← previous block·next block →recent activity