← previous blocknext block →recent activity
Analyzing
Block #97,515,208
48 transactions · 46 stateful · 2026-08-20 03:11:40 UTC
Parallelism
71/100
Blocked
72%
Avg conflicts / tx
2.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,515,208 · 48 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w07w18w19w210w211w312w313w414w515w620w329w832w1034w235w137w239w140w341w347w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0xe606662e…0efc
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0xc87603d5…8ba0
0x34b655…2a6f
10 touches
10 conflicts
0x9077b7f8…f30e
0x34b655…2a6f
10 touches
10 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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity