← previous blocknext block →recent activity
Analyzing
Block #97,629,461
16 transactions · 15 stateful · 2026-08-20 12:49:28 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,629,461 · 16 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
1w04w06w07w111w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x317e7ae5…61f0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x30408827…9206
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xfd5d46d5…52ad
0x34b655…2a6f
4 touches
1 conflict
0xa21abc5d…b512
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
1 conflict on slot 0x317e7ae581…6b61f0
Audit this contract →
← previous block·next block →recent activity