← previous blocknext block →recent activity
Analyzing
Block #106,404,972
22 transactions · 21 stateful · 2026-09-20 07:35:11 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,404,972 · 22 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
1w02w13w24w35w26w312w013w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cad7cc…db3e
0x5be4ee…673f
7 touches
6 conflicts
0x7a3db8d6…5e36
0xd32edf…ff58
7 touches
6 conflicts
0xf6cad7cc…db30
0x5be4ee…673f
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xec85b41e…7c92
0x1b6862…e19c
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: 0x5be4ee8b…b7673f
6 conflicts on slot 0xf6cad7ccce…f9db3e
Audit this contract →
← previous block·next block →recent activity