← previous blocknext block →recent activity
Analyzing
Block #97,364,749
23 transactions · 19 stateful · 2026-08-19 14:11:15 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,364,749 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w37w08w19w215w316w417w418w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xaa9f27b0…9cf2
0x34b655…2a6f
8 touches
6 conflicts
0xaa3c2d90…e0ba
0x34b655…2a6f
8 touches
6 conflicts
0x0094c930…06df
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd0ec60a1…d246
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity