← previous blocknext block →recent activity
Analyzing
Block #97,629,210
83 transactions · 70 stateful · 2026-08-20 12:48:12 UTC
Parallelism
77/100
Blocked
79%
Avg conflicts / tx
4.8
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #97,629,210 · 83 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
1w03w14w05w16w27w311w415w516w617w718w819w920w1022w1123w1225w1326w1427w1528w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x00000000…003d
0xa6afd3…d132
22 touches
55 conflicts
0xdc5d380d…4bbd
0xa6afd3…d132
22 touches
55 conflicts
0xa7a95fdb…5102
0xa6afd3…d132
22 touches
55 conflicts
0xea7ebe9d…709e
0x2b46c0…1669
20 touches
45 conflicts
0x5778d110…d2e6
0xc8689a…ee79
20 touches
45 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: 0x103de0b5…25bb55
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity