← previous blocknext block →recent activity
Analyzing
Block #106,283,047
40 transactions · 39 stateful · 2026-09-19 21:21:37 UTC
Parallelism
50/100
Blocked
79%
Avg conflicts / tx
3.92
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,283,047 · 40 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w58w613w114w234w435w536w639w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ea5b300…4b78
0x34b655…2a6f
24 touches
66 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
24 touches
66 conflicts
0x86cea35b…bdff
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0018
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0028
0x1b6862…e19c
12 touches
15 conflicts
0x1f8a126c…9aa1
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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
66 conflicts on slot 0x4ea5b30049…3e4b78
Audit this contract →
← previous block·next block →recent activity