← previous blocknext block →recent activity
Analyzing
Block #105,842,178
40 transactions · 32 stateful · 2026-09-18 08:21:34 UTC
Parallelism
73/100
Blocked
78%
Avg conflicts / tx
2.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,842,178 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w610w320w138w339w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x35801c67…bcc5
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity