← previous blocknext block →recent activity
Analyzing
Block #92,201,899
12 transactions · 8 stateful · 2026-08-01 12:26:20 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,201,899 · 12 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x1f02c5ca…02d7
0x34b655…2a6f
2 touches
0 conflicts
0x206ed0b7…7ee9
0x34b655…2a6f
2 touches
0 conflicts
0x21852c6f…fd6f
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e2
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e3
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 0x9b2d3bee9d…d68eeb
Audit this contract →
← previous block·next block →recent activity