pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,935,725
← previous block
next block →
recent activity
Analyzing
Block #101,935,725
12 transactions · 12 stateful · 2026-09-04 15:25:55 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,935,725
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
mint
· blocks 2
#5
0x5acec890
#6
0x5acec890
#7
0x59558d29
#8
poke
#9
setData
#10
execFwdPositionOpsV2
· blocks 1
#3
mint
· blocks 1
#11
execOrders
#4
mint
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e193234…b820
0x843c54…2fb5
6 touches
3 conflicts
0x1a1e6821…0510
0x843c54…2fb5
6 touches
3 conflicts
0xc58ce5dc…b851
0x843c54…2fb5
6 touches
3 conflicts
0x00000000…0002
0x843c54…2fb5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69d2053b…935a
0x34b655…2a6f
2 touches
0 conflicts
0x739123da…57f3
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:
0x843c5498…f62fb5
3 conflicts on slot
0x0e19323450…06b820
Audit this contract →
← previous block
·
next block →
recent activity