← previous blocknext block →recent activity
Analyzing
Block #104,869,022
25 transactions · 25 stateful · 2026-09-14 22:42:22 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,869,022 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w18w211w315w316w417w519w221w323w024w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62023181…811e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe86dd774…6c20
0x34b655…2a6f
6 touches
3 conflicts
0xf49aa5ae…67c0
0x34b655…2a6f
6 touches
3 conflicts
0xd9722304…6ed0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6202318167…4d811e
Audit this contract →
← previous block·next block →recent activity