← previous blocknext block →recent activity
Analyzing
Block #96,220,314
9 transactions · 8 stateful · 2026-08-15 13:52:54 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,220,314 · 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
1w02w13w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x55b2f68b…829a
0x34b655…2a6f
4 touches
1 conflict
0x041bddcd…d2cf
0x34b655…2a6f
2 touches
0 conflicts
0x0759c8f2…8408
0x34b655…2a6f
2 touches
0 conflicts
0x388633a0…86cd
0x34b655…2a6f
2 touches
0 conflicts
0x45b3c66c…b788
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity