← previous blocknext block →recent activity
Analyzing
Block #97,519,440
50 transactions · 46 stateful · 2026-08-20 03:32:58 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.38
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,519,440 · 50 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w39w411w013w014w115w117w219w321w523w624w728w1029w1135w140w241w342w446w1349w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0x1ba73d09…ba89
0x34b655…2a6f
10 touches
10 conflicts
0x21d6593f…26e1
0x34b655…2a6f
10 touches
10 conflicts
0x38c47502…1005
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
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
21 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity