← previous blocknext block →recent activity
Analyzing
Block #97,739,593
11 transactions · 11 stateful · 2026-08-20 22:13:22 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,739,593 · 11 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
2w03w04w15w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b437d40…654d
0x34b655…2a6f
6 touches
3 conflicts
0x11b3bcf6…fe81
0x34b655…2a6f
4 touches
1 conflict
0x247c79f2…e698
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
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
3 conflicts on slot 0x0b437d4083…60654d
Audit this contract →
← previous block·next block →recent activity