← previous blocknext block →recent activity
Analyzing
Block #97,502,522
20 transactions · 18 stateful · 2026-08-20 02:07:50 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,502,522 · 20 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
1w02w03w05w06w17w28w19w010w111w113w216w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70e505c7…c1d0
0x34b655…2a6f
6 touches
3 conflicts
0x655aa1bb…138c
0x40c49f…2af0
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xec85b41e…7c90
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 0x70e505c759…7cc1d0
Audit this contract →
← previous block·next block →recent activity