← previous blocknext block →recent activity
Analyzing
Block #106,188,003
28 transactions · 26 stateful · 2026-09-19 13:23:12 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.82
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,188,003 · 28 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w211w012w113w314w415w517w618w719w820w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046776c6…e120
0x34b655…2a6f
14 touches
21 conflicts
0xd62f3741…b903
0x34b655…2a6f
14 touches
21 conflicts
0xbb2316a2…23cd
0x34b655…2a6f
8 touches
6 conflicts
0xd9ddc6d5…86a2
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
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: Perpl
21 conflicts on slot 0x046776c66d…81e120
Audit this contract →
← previous block·next block →recent activity