← previous blocknext block →recent activity
Analyzing
Block #92,311,986
19 transactions · 17 stateful · 2026-08-01 21:40:01 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,311,986 · 19 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
2w03w14w05w06w18w110w211w012w113w214w315w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xffb2bfcf…b92a
0x34b655…2a6f
6 touches
3 conflicts
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x5cabd02a…a05f
0x34b655…2a6f
4 touches
1 conflict
0x7175a904…640c
0x34b655…2a6f
4 touches
1 conflict
0x94aff148…b584
0x34b655…2a6f
4 touches
1 conflict
0xa4e368da…ed39
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity