← previous blocknext block →recent activity
Analyzing
Block #97,197,303
21 transactions · 15 stateful · 2026-08-19 00:00:17 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,197,303 · 21 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
1w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x809f2ba8…89d3
0x34b655…2a6f
4 touches
1 conflict
0x8bb5c3e4…6da4
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf8e8419…c691
0x34b655…2a6f
4 touches
1 conflict
0xf64639f2…bd9c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x47ed8e43…8a8a
0x851145…3f07
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 0x809f2ba80d…9489d3
Audit this contract →
← previous block·next block →recent activity