← previous blocknext block →recent activity
Analyzing
Block #106,199,405
24 transactions · 23 stateful · 2026-09-19 14:20:35 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,405 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w012w013w114w216w217w318w419w520w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x8dc6c70d…37a6
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x5d22710e…af04
0x34b655…2a6f
8 touches
6 conflicts
0x10805174…6b29
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity