← previous blocknext block →recent activity
Analyzing
Block #97,825,571
20 transactions · 19 stateful · 2026-08-21 05:27:27 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,825,571 · 20 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
1w02w13w04w05w16w17w28w310w311w412w514w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921893c3…b9b6
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x78e3ec57…8bf9
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x6636a104…d595
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 0x921893c31c…45b9b6
Audit this contract →
← previous block·next block →recent activity