← previous blocknext block →recent activity
Analyzing
Block #104,847,179
33 transactions · 28 stateful · 2026-09-14 20:52:23 UTC
Parallelism
79/100
Blocked
61%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,847,179 · 33 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
1w02w13w25w26w37w411w315w416w417w523w524w629w131w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c168b41…7486
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xf575098f…cb19
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9a0016b5…4c4f
0xa6afd3…d132
6 touches
3 conflicts
0x502b3ee1…7f7c
0x34b655…2a6f
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 0x9c168b41b3…567486
Audit this contract →
← previous block·next block →recent activity