← previous blocknext block →recent activity
Analyzing
Block #97,602,489
31 transactions · 29 stateful · 2026-08-20 10:33:11 UTC
Parallelism
58/100
Blocked
69%
Avg conflicts / tx
2.65
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,602,489 · 31 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w08w19w110w211w312w313w414w215w317w118w419w523w626w927w1028w1129w1230w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40ac662f…df77
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x0a54ab40…d4b4
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x40ac662f45…43df77
Audit this contract →
← previous block·next block →recent activity