← previous blocknext block →recent activity
Analyzing
Block #96,035,772
12 transactions · 12 stateful · 2026-08-14 22:24:42 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,035,772 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb44cedd…c666
0x34b655…2a6f
6 touches
3 conflicts
0x38903dee…3c17
0x34b655…2a6f
4 touches
1 conflict
0x71e1dee6…d11b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x154594d5…564e
0x34b655…2a6f
2 touches
0 conflicts
0x1ecde9da…3735
0x34b655…2a6f
2 touches
0 conflicts
0x2b17ed65…ecf8
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 0xbb44cedda5…77c666
Audit this contract →
← previous block·next block →recent activity