← previous blocknext block →recent activity
Analyzing
Block #106,464,049
24 transactions · 22 stateful · 2026-09-20 12:32:34 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,464,049 · 24 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
1w02w13w24w05w16w27w38w49w210w315w017w119w020w121w222w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa386bf35…7e9f
0x34b655…2a6f
10 touches
10 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
10 touches
10 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
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0463db49…5d05
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 0xa386bf35b9…dd7e9f
Audit this contract →
← previous block·next block →recent activity