pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,453,604
← previous block
next block →
recent activity
Analyzing
Block #100,453,604
12 transactions · 10 stateful · 2026-08-30 11:07:14 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,453,604
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
execOrders
· blocks 1
#6
0x0c7abd22
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
setData
#10
execFwdPositionOpsV2
#11
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0960ac51…5440
0x34b655…2a6f
2 touches
0 conflicts
0x201e862b…122f
0x34b655…2a6f
2 touches
0 conflicts
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x55982cd0…1930
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
0xfe45073ed9…0c6315
Audit this contract →
← previous block
·
next block →
recent activity