← previous blocknext block →recent activity
Analyzing
Block #106,215,655
60 transactions · 53 stateful · 2026-09-19 15:42:25 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
2.18
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,215,655 · 60 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w112w213w324w228w329w430w531w639w740w841w942w1043w1144w1245w1346w1447w1448w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
24 touches
66 conflicts
0xa3700f09…bac2
0x34b655…2a6f
16 touches
28 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0x2e90dcf9…1289
0x34b655…2a6f
14 touches
21 conflicts
0xd597209e…9800
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
10 touches
10 conflicts
0x647643a2…284e
0x34b655…2a6f
8 touches
6 conflicts
0x742436a7…c4d4
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity