← previous blocknext block →recent activity
Analyzing
Block #106,389,265
17 transactions · 16 stateful · 2026-09-20 06:16:09 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,389,265 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w111w012w113w214w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60666ae8…3efa
0x5be4ee…673f
7 touches
6 conflicts
0x60666ae8…3eec
0x5be4ee…673f
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x69017fce…85bd
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x60666ae8ec…593efa
Audit this contract →
← previous block·next block →recent activity