← previous blocknext block →recent activity
Analyzing
Block #97,820,414
15 transactions · 14 stateful · 2026-08-21 05:01:28 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,820,414 · 15 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
1w02w15w26w312w014w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0x1eec16a0…9e8c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x3bc1f8bd…2b33
0x34b655…2a6f
2 touches
0 conflicts
0x4de40a98…ee65
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 0xac206e4761…ffef7d
Audit this contract →
← previous block·next block →recent activity