pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,700,614
← previous block
next block →
recent activity
Analyzing
Block #100,700,614
12 transactions · 12 stateful · 2026-08-31 07:49:48 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,700,614
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#6
execFwdPositionOpsV2
#7
placeAndExecuteMarketSell
#8
executeBatch
#9
transferWithAuthorization
#10
setData
#11
execOrders
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x5947e5b2…3625
0x34b655…2a6f
2 touches
0 conflicts
0x5e8223c2…c242
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x78860c4f…cade
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
0x02373c432b…ff3cb3
Audit this contract →
← previous block
·
next block →
recent activity