← previous blocknext block →recent activity
Analyzing
Block #97,478,285
22 transactions · 20 stateful · 2026-08-20 00:05:55 UTC
Parallelism
82/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,478,285 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w27w010w011w112w113w215w116w217w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0x3fd594dc…e157
0xd32edf…ff58
5 touches
3 conflicts
0x63bed776…8d4a
0x34b655…2a6f
4 touches
1 conflict
0xad10fa59…a3db
0x34b655…2a6f
4 touches
1 conflict
0x53dcbe77…b8e8
0x34b655…2a6f
4 touches
1 conflict
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity