← previous blocknext block →recent activity
Analyzing
Block #96,838,864
14 transactions · 13 stateful · 2026-08-17 17:44:16 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,838,864 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
8 touches
6 conflicts
0xc467a38b…cf75
0x34b655…2a6f
8 touches
6 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
4 touches
1 conflict
0x77f5ee28…347d
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity