← previous blocknext block →recent activity
Analyzing
Block #106,468,365
19 transactions · 19 stateful · 2026-09-20 12:54:18 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,468,365 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w011w212w213w314w417w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505b587d…5d6a
0x34b655…2a6f
10 touches
10 conflicts
0x41b09600…3c38
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x4423a307…9f46
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x505b587dfa…535d6a
Audit this contract →
← previous block·next block →recent activity