← previous blocknext block →recent activity
Analyzing
Block #97,551,476
25 transactions · 24 stateful · 2026-08-20 06:14:21 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,551,476 · 25 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
1w02w08w09w111w012w013w114w217w118w319w220w321w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8544535…b3d1
0x34b655…2a6f
8 touches
6 conflicts
0x0304ed8a…9f25
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
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 0xc854453592…47b3d1
Audit this contract →
← previous block·next block →recent activity