← previous blocknext block →recent activity
Analyzing
Block #97,666,260
21 transactions · 19 stateful · 2026-08-20 16:00:34 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,666,260 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w08w19w110w211w312w415w516w617w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xca1360af…ca87
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity