← previous blocknext block →recent activity
Analyzing
Block #97,197,514
24 transactions · 20 stateful · 2026-08-19 00:01:20 UTC
Parallelism
92/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,197,514 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w116w019w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56902411…e0ce
0x34b655…2a6f
4 touches
1 conflict
0x60a899fe…e7a2
0x34b655…2a6f
4 touches
1 conflict
0x346a6959…7302
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0xf64639f2…bd9c
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x50fd6f6f…2048
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
1 conflict on slot 0x5690241144…48e0ce
Audit this contract →
← previous block·next block →recent activity