← previous blocknext block →recent activity
Analyzing
Block #98,013,135
26 transactions · 21 stateful · 2026-08-21 21:24:08 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,013,135 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w19w011w112w217w018w120w221w322w423w524w625w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x38963aeb…c33f
0xa6afd3…d132
6 touches
3 conflicts
0x39773cec…38ed
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity