pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,582,019
← previous block
next block →
recent activity
Analyzing
Block #105,582,019
12 transactions · 12 stateful · 2026-09-17 10:30:49 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,582,019
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
0x5acec890
· blocks 1
#6
0x5acec890
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#10
transfer
#2
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ec31060…f25e
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0xf18803af…e7a5
0x34b655…2a6f
4 touches
1 conflict
0x232df012…c608
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x0bb45478…05cb
0x34b655…2a6f
2 touches
0 conflicts
0x0f64663a…6e0d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x7ec3106046…c2f25e
Audit this contract →
← previous block
·
next block →
recent activity