← previous blocknext block →recent activity
Analyzing
Block #97,385,472
52 transactions · 48 stateful · 2026-08-19 16:01:38 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.67
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #97,385,472 · 52 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
2w04w05w16w27w39w010w112w215w218w425w626w528w329w130w231w632w733w834w936w1044w1150w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xcd91995d…15c7
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc3961304…d676
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x2029b74e…c206
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
55 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity