← previous blocknext block →recent activity
Analyzing
Block #96,221,789
13 transactions · 11 stateful · 2026-08-15 14:00:19 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,221,789 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x628359b1…7263
0x34b655…2a6f
6 touches
3 conflicts
0xf5fefc40…8baf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x8a1e429b…f85c
0x34b655…2a6f
4 touches
1 conflict
0x8d3e8f8c…8de4
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
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 0x628359b1c9…1a7263
Audit this contract →
← previous block·next block →recent activity