pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,696,086
← previous block
next block →
recent activity
Analyzing
Block #104,696,086
11 transactions · 10 stateful · 2026-09-14 08:09:18 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,696,086
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0xab083028
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
setData
#8
0x519a6414
· blocks 1
#10
execOrders
#9
0x519a6414
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0xd7e97d…f164
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x971f63ee…1f24
0x754704…b603
2 touches
0 conflicts
0xb7f9a293…6bca
0x754704…b603
2 touches
0 conflicts
0xde39c8f7…33f7
0x754704…b603
2 touches
0 conflicts
0x2021eea2…f97c
0x99c7a7…8bf0
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:
0xd7e97da3…b7f164
1 conflict on slot
0x0000000000…000008
Audit this contract →
← previous block
·
next block →
recent activity