← previous blocknext block →recent activity
Analyzing
Block #106,950,778
25 transactions · 24 stateful · 2026-09-22 05:23:19 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,950,778 · 25 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
2w05w16w27w08w19w210w311w415w218w319w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa448c490…367c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x574628e9…dcc3
0x34b655…2a6f
10 touches
10 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
10 touches
10 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
0x34b655…2a6f
6 touches
3 conflicts
0x3f2168b4…37b5
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 0xa448c490c4…94367c
Audit this contract →
← previous block·next block →recent activity