← previous blocknext block →recent activity
Analyzing
Block #97,558,184
51 transactions · 46 stateful · 2026-08-20 06:48:43 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.9
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,558,184 · 51 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
1w03w05w07w19w010w111w012w013w114w215w216w317w318w419w420w521w522w623w724w725w826w939w1341w242w343w650w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x728f999a…832f
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x6737ee07…9978
0x34b655…2a6f
8 touches
6 conflicts
0x75fe24d2…46f9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xce163d4f…b563
0xa6afd3…d132
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
28 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity