← previous blocknext block →recent activity
Analyzing
Block #97,825,483
14 transactions · 14 stateful · 2026-08-21 05:27:00 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,825,483 · 14 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
1w02w13w04w15w26w27w38w412w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf10b6c3…c186
0x34b655…2a6f
6 touches
3 conflicts
0x61a46e28…ec92
0x34b655…2a6f
6 touches
3 conflicts
0xe38f7c29…72fc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x872e51c8…ae2c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
3 conflicts on slot 0xcf10b6c388…63c186
Audit this contract →
← previous block·next block →recent activity