pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,681,200
← previous block
next block →
recent activity
Analyzing
Block #101,681,200
11 transactions · 11 stateful · 2026-09-03 18:03:48 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,681,200
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
#4
forward
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
· blocks 1
#7
forward
#9
setData
#10
execOrders
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x041d6cf6…e9d7
0x34b655…2a6f
2 touches
0 conflicts
0x0b7b942e…f3f4
0x34b655…2a6f
2 touches
0 conflicts
0x123a68b3…202a
0x34b655…2a6f
2 touches
0 conflicts
0x2dfba473…d9a6
0x34b655…2a6f
2 touches
0 conflicts
0x2e05467a…e3b3
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity