← previous blocknext block →recent activity
Analyzing
Block #97,614,009
67 transactions · 51 stateful · 2026-08-20 11:31:43 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
2.66
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #97,614,009 · 67 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w29w018w226w427w528w630w731w832w933w1035w1136w1238w1339w143w1044w1445w847w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x84611dd3…b344
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity