← previous blocknext block →recent activity
Analyzing
Block #91,129,184
8 transactions · 7 stateful · 2026-07-28 18:27:50 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,129,184 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc0e9c8…3ae6
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd81dbbb9…d0c5
0x34b655…2a6f
4 touches
1 conflict
0x0d9a041b…c6ec
0x34b655…2a6f
2 touches
0 conflicts
0x122b1c2b…1415
0x34b655…2a6f
2 touches
0 conflicts
0x29041471…d37a
0x34b655…2a6f
2 touches
0 conflicts
0x3601aa45…29cb
0x34b655…2a6f
2 touches
0 conflicts
0x423c2d5e…0547
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
1 conflict on slot 0x5cc0e9c8b0…1d3ae6
Audit this contract →
← previous block·next block →recent activity