← previous blocknext block →recent activity
Analyzing
Block #96,111,963
13 transactions · 11 stateful · 2026-08-15 04:47:53 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,111,963 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea290724…08fd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x29c1a140…099f
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x62738158…e746
0x34b655…2a6f
4 touches
1 conflict
0x910a6959…34b7
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
3 conflicts on slot 0xea290724cb…2b08fd
Audit this contract →
← previous block·next block →recent activity