← previous blocknext block →recent activity
Analyzing
Block #105,926,411
116 transactions · 83 stateful · 2026-09-18 15:26:31 UTC
Parallelism
84/100
Blocked
72%
Avg conflicts / tx
2.62
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #105,926,411 · 116 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w07w010w111w115w116w217w318w125w126w227w328w429w531w235w336w439w648w249w350w787w893w997w1098w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
36 touches
153 conflicts
0xaad6be10…0801
0x2a68ba…90c5
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0xf8014a03…b7c0
0xd32edf…ff58
13 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xcc8faac2…c766
0x065c9d…c394
12 touches
15 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: 0xf5b5f7f8…a36d70
153 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity