pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,332,483
← previous block
next block →
recent activity
Analyzing
Block #104,332,483
14 transactions · 13 stateful · 2026-09-13 01:23:34 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,332,483
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xefdb8189
· blocks 1
#3
0xab083028
#4
0xab083028
#5
execOrders
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
execPerpOps
#10
execPerpOps
#11
setData
#12
0x3f5c179b
#13
execFwdPositionOpsV2
#2
0xefdb8189
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6063a926…0be4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xab7f4e6b…8093
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
3 touches
1 conflict
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
0x6063a9268a…ea0be4
Audit this contract →
← previous block
·
next block →
recent activity