← previous blocknext block →recent activity
Analyzing
Block #96,604,726
21 transactions · 18 stateful · 2026-08-16 22:06:38 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,604,726 · 21 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
3w04w05w16w27w311w414w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x9fbc6a76…9c29
0x34b655…2a6f
4 touches
1 conflict
0x79adeae4…34ff
0x34b655…2a6f
4 touches
1 conflict
0xb6dea0c1…20ca
0x34b655…2a6f
4 touches
1 conflict
0xf7c661e2…011b
0x34b655…2a6f
4 touches
1 conflict
0xed445d9f…f3ff
0x34b655…2a6f
3 touches
1 conflict
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity