← previous blocknext block →recent activity
Analyzing
Block #97,466,714
22 transactions · 19 stateful · 2026-08-19 23:07:28 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,466,714 · 22 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
4w05w16w210w011w112w113w214w215w319w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
6 touches
3 conflicts
0x1867b653…e61b
0x34b655…2a6f
6 touches
3 conflicts
0x2ba49d29…0cd1
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity