← previous blocknext block →recent activity
Analyzing
Block #104,847,731
21 transactions · 19 stateful · 2026-09-14 20:55:09 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,847,731 · 21 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
1w02w13w24w35w46w07w18w29w310w417w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38aa1898…fdf5
0x3bd359…433a
10 touches
10 conflicts
0xeb6860e2…3ca4
0x93a451…d286
10 touches
10 conflicts
0xd06cc746…27e4
0x93a451…d286
10 touches
10 conflicts
0xebf7d7fd…0a99
0x188d58…ea8e
10 touches
10 conflicts
0xebf7d7fd…0a9a
0x188d58…ea8e
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 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: Wrapped MON (WMON)
10 conflicts on slot 0x38aa189812…48fdf5
Audit this contract →
← previous block·next block →recent activity