← previous blocknext block →recent activity
Analyzing
Block #97,604,244
51 transactions · 44 stateful · 2026-08-20 10:42:01 UTC
Parallelism
57/100
Blocked
77%
Avg conflicts / tx
3.71
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #97,604,244 · 51 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w17w28w29w310w311w413w414w515w625w736w939w1240w1350w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
30 touches
105 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x80eee557…711d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x103de0…bb55
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 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
105 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity