← previous blocknext block →recent activity
Analyzing
Block #98,773,494
50 transactions · 28 stateful · 2026-08-24 13:46:52 UTC
Parallelism
82/100
Blocked
64%
Avg conflicts / tx
1.14
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,773,494 · 50 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w010w112w217w119w221w323w424w525w635w436w739w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
6 touches
3 conflicts
0xc21def1b…c24d
0xa6afd3…d132
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity