← previous blocknext block →recent activity
Analyzing
Block #105,921,362
76 transactions · 51 stateful · 2026-09-18 15:01:06 UTC
Parallelism
70/100
Blocked
80%
Avg conflicts / tx
4
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #105,921,362 · 76 txs across 23 waves · depth 23
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
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w37w48w59w610w711w812w913w1015w1117w148w1270w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
38 touches
171 conflicts
0xaad6be10…0801
0x2a68ba…90c5
26 touches
78 conflicts
0x5ef326ed…69dc
0xa6afd3…d132
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x8b52b75c…8a0d
0xa6afd3…d132
18 touches
36 conflicts
0x0b104f98…d9ee
0xc8689a…ee79
16 touches
28 conflicts
0xabde8104…c9a9
0x2a68ba…90c5
16 touches
28 conflicts
0x8cf3d245…1d0d
0x34ae4d…3fc5
16 touches
28 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
171 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity