← previous blocknext block →recent activity
Analyzing
Block #96,212,414
13 transactions · 9 stateful · 2026-08-15 13:13:10 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,212,414 · 13 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
1w02w03w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ecb58c4…ac20
0x34b655…2a6f
4 touches
1 conflict
0xa02adf4b…8e11
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x46b225ff…9d21
0x34b655…2a6f
2 touches
0 conflicts
0x4acc6dca…a868
0x34b655…2a6f
2 touches
0 conflicts
0x56a284d9…32e4
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
1 conflict on slot 0x4ecb58c4e2…f9ac20
Audit this contract →
← previous block·next block →recent activity