← previous blocknext block →recent activity
Analyzing
Block #97,370,851
24 transactions · 23 stateful · 2026-08-19 14:42:22 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,370,851 · 24 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
1w02w03w14w05w16w07w18w011w012w117w118w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0x6676e4f3…6a9e
0x851145…3f07
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf18906a6…d2e3
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
3 conflicts on slot 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity