← previous blocknext block →recent activity
Analyzing
Block #106,206,872
27 transactions · 26 stateful · 2026-09-19 14:58:12 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,206,872 · 27 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
1w02w13w04w06w07w111w012w113w214w316w117w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c804088…250d
0x34b655…2a6f
14 touches
21 conflicts
0x98568c43…ff4e
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xe7045293…87b9
0x34b655…2a6f
8 touches
6 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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: Perpl
21 conflicts on slot 0x6c804088db…bb250d
Audit this contract →
← previous block·next block →recent activity