← previous blocknext block →recent activity
Analyzing
Block #106,381,722
19 transactions · 17 stateful · 2026-09-20 05:38:11 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,381,722 · 19 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
2w03w04w15w07w111w213w014w115w216w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa83fbc81…9e9c
0x5be4ee…673f
7 touches
6 conflicts
0xa83fbc81…9eaa
0x5be4ee…673f
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xa83fbc81fc…f99e9c
Audit this contract →
← previous block·next block →recent activity