← previous blocknext block →recent activity
Analyzing
Block #104,868,671
44 transactions · 36 stateful · 2026-09-14 22:40:36 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.41
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #104,868,671 · 44 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w011w012w113w214w116w317w418w519w620w721w827w931w133w234w235w236w337w440w341w1043w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
16 touches
28 conflicts
0x3b6e959d…158f
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xc69280be…07a0
0x34b655…2a6f
12 touches
15 conflicts
0x7b8b5ba9…7ab9
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
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
28 conflicts on slot 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity