← previous blocknext block →recent activity
Analyzing
Block #105,844,894
27 transactions · 25 stateful · 2026-09-18 08:35:21 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.85
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,844,894 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w210w413w317w418w519w620w721w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x7120873b…ac06
0x34b655…2a6f
12 touches
15 conflicts
0x2c0c3e3f…5849
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xac79a0c7…be16
0x1b6862…e19c
8 touches
6 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity