← previous blocknext block →recent activity
Analyzing
Block #97,398,172
20 transactions · 18 stateful · 2026-08-19 17:20:55 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,398,172 · 20 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
1w03w04w16w07w28w310w111w312w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb130b3…92e2
0x34b655…2a6f
8 touches
6 conflicts
0xb74116b4…dc4a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1ebd3ecc…1e4b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0xaeb130b322…bf92e2
Audit this contract →
← previous block·next block →recent activity