← previous blocknext block →recent activity
Analyzing
Block #106,337,569
21 transactions · 20 stateful · 2026-09-20 01:55:58 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,337,569 · 21 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
1w02w011w112w113w214w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6673358e…23d8
0x5be4ee…673f
7 touches
6 conflicts
0x6673358e…23e6
0x5be4ee…673f
7 touches
6 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3a7b2fc9…7197
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
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 0x6673358eae…4b23d8
Audit this contract →
← previous block·next block →recent activity