pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,797,990
← previous block
next block →
recent activity
Analyzing
Block #101,797,990
12 transactions · 12 stateful · 2026-09-04 03:51:13 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,797,990
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a9a40a9
#2
updatePrices
· blocks 1
#4
0x5acec890
· blocks 2
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
transfer
#9
execFwdPositionOpsV2
#10
setData
#3
updatePrices
#5
0x5acec890
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x03f79551…7bc7
0x34b655…2a6f
2 touches
0 conflicts
0x27a68c38…9741
0x34b655…2a6f
2 touches
0 conflicts
0x28189f22…a854
0x34b655…2a6f
2 touches
0 conflicts
0x3128419e…1d70
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:
0xf5b5f7f8…a36d70
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity