← previous blocknext block →recent activity
Analyzing
Block #97,728,016
63 transactions · 53 stateful · 2026-08-20 21:15:06 UTC
Parallelism
76/100
Blocked
66%
Avg conflicts / tx
1.57
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,728,016 · 63 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w19w010w011w213w014w118w019w120w221w323w124w227w028w129w233w343w145w449w550w554w655w757w1061w1462w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x6a9e408e…3721
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x3df3de0d…cd8b
0x34b655…2a6f
10 touches
10 conflicts
0x9587c5b4…f867
0xd32edf…ff58
9 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity