pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,748,477
← previous block
next block →
recent activity
Analyzing
Block #100,748,477
13 transactions · 12 stateful · 2026-08-31 11:50:34 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,748,477
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0xab083028
· blocks 1
#4
0x59558d29
#5
0x59558d29
#6
execOrders
#7
placeAndExecuteMarketSell
· blocks 1
#9
execFwdPositionOpsV2
#10
0x6a956b02
#11
setData
#12
execOrders
#3
0xab083028
#8
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4f6425eb…9a67
0x851145…3f07
4 touches
1 conflict
0xad47b33d…500b
0x754704…b603
2 touches
0 conflicts
0xf00d2133…d68e
0x754704…b603
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
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:
0x01bff417…bc1071
1 conflict on slot
0x11b69a7ea1…83334e
Audit this contract →
← previous block
·
next block →
recent activity