← previous blocknext block →recent activity
Analyzing
Block #97,614,605
17 transactions · 17 stateful · 2026-08-20 11:34:43 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,614,605 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w17w28w39w310w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26bbcb47…263f
0x34b655…2a6f
10 touches
10 conflicts
0xf3b83c6d…439a
0x34b655…2a6f
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x63ef59ea…c871
0x34b655…2a6f
4 touches
1 conflict
0x7f38bfbc…61e3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
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
10 conflicts on slot 0x26bbcb47b6…ee263f
Audit this contract →
← previous block·next block →recent activity