← previous blocknext block →recent activity
Analyzing
Block #97,733,566
16 transactions · 15 stateful · 2026-08-20 21:43:03 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,733,566 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w211w113w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xa3684bdf…7d99
0x34b655…2a6f
6 touches
3 conflicts
0xb17e70f9…3f4c
0x34b655…2a6f
4 touches
2 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x04b85c37…28b9
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
6 conflicts on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity