pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,500,960
← previous block
next block →
recent activity
Analyzing
Block #101,500,960
10 transactions · 8 stateful · 2026-09-03 02:57:05 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,500,960
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x41a8f47c
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
0xe3a3c9cc
#5
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
· blocks 1
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x26d8622c…e8af
0x34b655…2a6f
2 touches
0 conflicts
0x6ca407b4…1edc
0x34b655…2a6f
2 touches
0 conflicts
0x6de748bb…eb4c
0x34b655…2a6f
2 touches
0 conflicts
0x839c0c71…bada
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
0x51fc8795c8…57126f
Audit this contract →
← previous block
·
next block →
recent activity