← previous blocknext block →recent activity
Analyzing
Block #96,491,022
13 transactions · 11 stateful · 2026-08-16 12:34:27 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,491,022 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ab6fca5…de5c
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x10c76789…5350
0x34b655…2a6f
9 touches
10 conflicts
0xf5f815e7…c83e
0x34b655…2a6f
8 touches
6 conflicts
0xbffde283…3385
0x34b655…2a6f
8 touches
6 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x9ab6fca525…66de5c
Audit this contract →
← previous block·next block →recent activity