← previous blocknext block →recent activity
Analyzing
Block #106,342,524
25 transactions · 23 stateful · 2026-09-20 02:20:54 UTC
Parallelism
80/100
Blocked
65%
Avg conflicts / tx
1.12
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,342,524 · 25 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
1w02w13w24w39w010w111w112w113w315w416w017w118w219w320w422w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x301ac4d6…334c
0x5be4ee…673f
9 touches
10 conflicts
0x301ac4d6…335a
0x5be4ee…673f
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: 0x5be4ee8b…b7673f
10 conflicts on slot 0x301ac4d667…c5334c
Audit this contract →
← previous block·next block →recent activity