pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,078,765
← previous block
next block →
recent activity
Analyzing
Block #102,078,765
12 transactions · 12 stateful · 2026-09-05 03:31:11 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,078,765
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
execOrders
· blocks 2
#3
0xab083028
#4
updateDataFeedsValuesPartial
#6
0x5acec890
#7
0x5acec890
#8
execOrders
#9
setData
#10
execFwdPositionOpsV2
#5
0x5acec890
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9feec606…4ad5
0x34b655…2a6f
4 touches
1 conflict
0xae8a7697…9685
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x02372d42…1871
0x34b655…2a6f
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x07c1664b…ce84
0x34b655…2a6f
2 touches
0 conflicts
0x26c599c1…706c
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
0x9feec6068d…354ad5
Audit this contract →
← previous block
·
next block →
recent activity