← previous blocknext block →recent activity
Analyzing
Block #98,567,581
28 transactions · 25 stateful · 2026-08-23 20:07:50 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,567,581 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w112w113w215w017w018w120w121w222w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a3a7c1…1e2b
0x0cc9b2…7777
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0002
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x5a598bc7…3801
0xd32edf…ff58
5 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: MONI (MONI)
3 conflicts on slot 0x99a3a7c17c…081e2b
Audit this contract →
← previous block·next block →recent activity