← previous blocknext block →recent activity
Analyzing
Block #96,483,121
7 transactions · 6 stateful · 2026-08-16 11:54:43 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,483,121 · 7 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x12f97307…97c3
0x34b655…2a6f
4 touches
1 conflict
0x68ca40a2…bc7c
0x34b655…2a6f
4 touches
1 conflict
0x841c22c4…10c6
0x34b655…2a6f
4 touches
1 conflict
0x096c7f83…68af
0x34b655…2a6f
2 touches
0 conflicts
0x0cdc38ed…c280
0x34b655…2a6f
2 touches
0 conflicts
0x1646c3e0…448e
0x34b655…2a6f
2 touches
0 conflicts
0x24d1b62e…d6e8
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 0x07bb3f5a12…2d617e
Audit this contract →
← previous block·next block →recent activity