← previous blocknext block →recent activity
Analyzing
Block #106,430,434
18 transactions · 16 stateful · 2026-09-20 09:43:20 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,430,434 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w210w311w412w513w614w716w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbc95f8d…95ab
0x34b655…2a6f
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x0307261f…c2d2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xf0e459f7…c5cb
0xd32edf…ff58
5 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: Perpl
6 conflicts on slot 0xfbc95f8d64…e495ab
Audit this contract →
← previous block·next block →recent activity