← previous blocknext block →recent activity
Analyzing
Block #97,724,884
36 transactions · 35 stateful · 2026-08-20 20:59:16 UTC
Parallelism
53/100
Blocked
66%
Avg conflicts / tx
2.47
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,724,884 · 36 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w28w09w010w312w414w515w416w517w618w719w820w924w1225w1326w1427w129w1530w134w1635w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbea60fe6…27c7
0x34b655…2a6f
10 touches
10 conflicts
0x422f657b…279e
0x34b655…2a6f
10 touches
10 conflicts
0x1bc9b1ca…85ef
0x34b655…2a6f
8 touches
6 conflicts
0x247c79f2…e698
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity