← previous blocknext block →recent activity
Analyzing
Block #97,603,160
14 transactions · 13 stateful · 2026-08-20 10:36:34 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,603,160 · 14 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
1w04w06w08w19w211w312w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80eee557…711d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
0x34b655…2a6f
4 touches
1 conflict
0x136b9738…5504
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 0x80eee55732…76711d
Audit this contract →
← previous block·next block →recent activity