← previous blocknext block →recent activity
Analyzing
Block #106,186,670
24 transactions · 22 stateful · 2026-09-19 13:16:30 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,186,670 · 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
2w03w14w26w07w18w013w316w017w119w420w121w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b713a9f…c0be
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd62f3741…b903
0x34b655…2a6f
6 touches
3 conflicts
0x365ac362…90c5
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x74200327…23ac
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
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
10 conflicts on slot 0x7b713a9fb6…cdc0be
Audit this contract →
← previous block·next block →recent activity