pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,374,049
← previous block
next block →
recent activity
Analyzing
Block #102,374,049
13 transactions · 10 stateful · 2026-09-06 04:27:28 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,374,049
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xefdb8189
· blocks 1
#3
0x0c7abd22
#4
0xa96df62f
#5
updatePrices
#6
0x59558d29
#7
execPerpOps
#8
execPerpOps
#9
execPerpOps
#10
execPerpOps
#11
setData
#12
0x6a9cebb3
#2
execOrders
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
0xf1894e7f…30fe
0x34b655…2a6f
4 touches
1 conflict
0x44f26cbe…58c2
0x34b655…2a6f
4 touches
1 conflict
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0xab7f4e6b…8093
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0x290abc80…f605
0x34b655…2a6f
2 touches
0 conflicts
0x444a6cf3…f22b
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
0xf1894e7f22…6c30fe
Audit this contract →
← previous block
·
next block →
recent activity