← previous blocknext block →recent activity
Analyzing
Block #105,852,398
36 transactions · 33 stateful · 2026-09-18 09:13:08 UTC
Parallelism
78/100
Blocked
58%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,852,398 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w110w222w323w424w525w526w627w733w334w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef8f176a…ed6d
0x34b655…2a6f
12 touches
15 conflicts
0xac61e951…28dc
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x1da7723c…80ae
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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
15 conflicts on slot 0xef8f176a73…8ded6d
Audit this contract →
← previous block·next block →recent activity