pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,056,936
← previous block
next block →
recent activity
Analyzing
Block #100,056,936
11 transactions · 10 stateful · 2026-08-29 01:46:59 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
#100,056,936
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execOrders
#4
transfer
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
0x927825be
#9
0x6a923a8a
#10
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0xc6457c2d…76d7
0x34b655…2a6f
4 touches
1 conflict
0xc6457c2d…76d8
0x34b655…2a6f
4 touches
1 conflict
0x408db73d…6e90
0x34b655…2a6f
4 touches
1 conflict
0x18fb40e9…0f6d
0x34b655…2a6f
2 touches
0 conflicts
0x2d9fc028…5b85
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…5990
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
0x0ed7cc0b4b…d2ee52
Audit this contract →
← previous block
·
next block →
recent activity