← previous blocknext block →recent activity
Analyzing
Block #105,849,501
81 transactions · 58 stateful · 2026-09-18 08:58:33 UTC
Parallelism
79/100
Blocked
72%
Avg conflicts / tx
2.46
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,849,501 · 81 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
1w02w05w16w07w19w211w112w317w118w219w320w421w522w645w448w550w1259w1368w277w1378w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x5fad6fee…7714
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x0a3e6786…cdaa
0x34b655…2a6f
12 touches
15 conflicts
0x3bca67b5…842d
0x34b655…2a6f
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: Perpl
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity