← previous blocknext block →recent activity
Analyzing
Block #97,384,265
59 transactions · 51 stateful · 2026-08-19 15:52:55 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.93
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,384,265 · 59 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w17w08w19w212w013w014w115w116w217w218w319w320w421w522w523w624w736w337w243w854w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0xbdcff57a…6ea3
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x87cf3bc6…74e1
0x34b655…2a6f
8 touches
6 conflicts
0x5d7e0e69…e6d2
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
28 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity