← previous blocknext block →recent activity
Analyzing
Block #97,480,285
20 transactions · 18 stateful · 2026-08-20 00:15:59 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,480,285 · 20 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
3w04w07w19w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x516e9b35…57e7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0xf3ba6d02…c7e2
0x34b655…2a6f
4 touches
1 conflict
0xe65d7198…ba41
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0x7aada5bb…c8f0
0x98dc6e…8633
2 touches
0 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 0x516e9b35e5…8857e7
Audit this contract →
← previous block·next block →recent activity