← previous blocknext block →recent activity
Analyzing
Block #98,026,429
22 transactions · 17 stateful · 2026-08-21 22:31:11 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,026,429 · 22 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
2w03w15w210w011w112w213w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x213ee207…a151
0x2b46c0…1669
6 touches
3 conflicts
0x46279ae7…20dd
0x2b46c0…1669
6 touches
3 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
6 touches
3 conflicts
0xdeed550b…338b
0x2b46c0…1669
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: 0x40c49f17…d22af0
6 conflicts on slot 0x065ff70bfe…b9356d
Audit this contract →
← previous block·next block →recent activity