← previous blocknext block →recent activity
Analyzing
Block #92,110,581
9 transactions · 7 stateful · 2026-08-01 04:47:04 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,110,581 · 9 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38eb2fc…1658
0x34b655…2a6f
4 touches
1 conflict
0xa38eb2fc…1659
0x34b655…2a6f
4 touches
1 conflict
0x155cce4c…007e
0x34b655…2a6f
3 touches
1 conflict
0xd0538ec1…abeb
0x34b655…2a6f
3 touches
1 conflict
0x1f6f8ff8…a5d4
0x34b655…2a6f
2 touches
0 conflicts
0x1f6f8ff8…a5d5
0x34b655…2a6f
2 touches
0 conflicts
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
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 0xa38eb2fcd4…781658
Audit this contract →
← previous block·next block →recent activity