← previous blocknext block →recent activity
Analyzing
Block #97,501,664
26 transactions · 21 stateful · 2026-08-20 02:03:31 UTC
Parallelism
62/100
Blocked
67%
Avg conflicts / tx
1.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #97,501,664 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w09w310w411w512w513w614w716w318w819w423w925w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x779cc2f3…fde1
0x34b655…2a6f
8 touches
6 conflicts
0xa21e8abe…a7f1
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
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 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity