← previous blocknext block →recent activity
Analyzing
Block #96,087,641
10 transactions · 9 stateful · 2026-08-15 02:45:34 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,087,641 · 10 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
4w05w06w1
- 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
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x8aa29f68…5645
0x34b655…2a6f
4 touches
1 conflict
0xa08db5f5…6d2a
0x754704…b603
2 touches
0 conflicts
0xa8669ab5…6af7
0x754704…b603
2 touches
0 conflicts
0xaf831072…51d5
0x80f006…d585
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