← previous blocknext block →recent activity
Analyzing
Block #96,597,515
9 transactions · 9 stateful · 2026-08-16 21:30:22 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,597,515 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ab6fca5…de5c
0x34b655…2a6f
6 touches
3 conflicts
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x420085f5…e2c2
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f1
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f2
0x34b655…2a6f
2 touches
0 conflicts
0x5e800a72…0189
0x34b655…2a6f
2 touches
0 conflicts
0x63a8652c…5b43
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 0x9ab6fca525…66de5c
Audit this contract →
← previous block·next block →recent activity