← previous blocknext block →recent activity
Analyzing
Block #106,586,053
25 transactions · 23 stateful · 2026-09-20 22:46:36 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.36
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,586,053 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w19w211w212w214w215w316w417w518w619w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6603a09f…6ad7
0x34b655…2a6f
12 touches
15 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x10b1245e…de66
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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
15 conflicts on slot 0x6603a09f57…446ad7
Audit this contract →
← previous block·next block →recent activity