← previous blocknext block →recent activity
Analyzing
Block #92,222,232
14 transactions · 13 stateful · 2026-08-01 14:08:35 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,222,232 · 14 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
2w04w15w06w17w28w29w210w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf9ccdb1…d44d
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x79e8f935…c3b6
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 0xaf9ccdb17e…8cd44d
Audit this contract →
← previous block·next block →recent activity