← previous blocknext block →recent activity
Analyzing
Block #97,386,370
33 transactions · 19 stateful · 2026-08-19 16:08:16 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,386,370 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w08w19w112w213w314w423w026w127w028w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4af1f77…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x037a4023…1f5a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4a458a56…c8ec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0xf4af1f773e…3c2a2f
Audit this contract →
← previous block·next block →recent activity