← previous blocknext block →recent activity
Analyzing
Block #91,425,380
15 transactions · 15 stateful · 2026-07-29 19:20:10 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,425,380 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w17w28w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41cf8311…38c7
0x34b655…2a6f
6 touches
3 conflicts
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x0802d0d8…dd0c
0x34b655…2a6f
4 touches
1 conflict
0x1781ea13…2f08
0x34b655…2a6f
4 touches
1 conflict
0x39f62455…741c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d3eebe6…a3da
0x34b655…2a6f
4 touches
1 conflict
0x5a4d5f09…5094
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 0x41cf831107…cb38c7
Audit this contract →
← previous block·next block →recent activity