← previous blocknext block →recent activity
Analyzing
Block #97,528,305
27 transactions · 23 stateful · 2026-08-20 04:17:33 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,528,305 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w08w19w210w311w417w118w521w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x85054dde…45f1
0x34b655…2a6f
8 touches
6 conflicts
0x25d909da…1722
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2ba49d29…0cd1
0x34b655…2a6f
4 touches
1 conflict
0x302f7678…c85e
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity