← previous blocknext block →recent activity
Analyzing
Block #105,760,519
31 transactions · 31 stateful · 2026-09-18 01:29:17 UTC
Parallelism
45/100
Blocked
65%
Avg conflicts / tx
3.29
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,760,519 · 31 txs across 17 waves · depth 17
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
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w415w516w517w618w719w820w921w1022w1023w1124w1225w1326w1427w1529w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5b61a2…b2bc
0x34b655…2a6f
18 touches
36 conflicts
0x548c15a4…0aba
0x34b655…2a6f
16 touches
28 conflicts
0x8b7c4de1…fdc6
0x34b655…2a6f
16 touches
28 conflicts
0x1204f20c…3f98
0x34b655…2a6f
14 touches
21 conflicts
0x70f537e8…399b
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x0efc210e…70ab
0x34b655…2a6f
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: Perpl
36 conflicts on slot 0xeb5b61a29c…4fb2bc
Audit this contract →
← previous block·next block →recent activity