← previous blocknext block →recent activity
Analyzing
Block #97,368,154
15 transactions · 13 stateful · 2026-08-19 14:28:37 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,368,154 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w18w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6871da4…e5dd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x731f2745…9370
0xa6afd3…d132
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x2f4b2cf9…4e1e
0x2b46c0…1669
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 0xb6871da418…c0e5dd
Audit this contract →
← previous block·next block →recent activity