pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,031,456
← previous block
next block →
recent activity
Analyzing
Block #100,031,456
12 transactions · 10 stateful · 2026-08-28 23:38:44 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,031,456
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
0x5acec890
#4
updatePrices
· blocks 2
#7
execOrders
#8
updateDataFeedsValuesPartial
#9
setData
#10
batchUpdate
#11
execFwdPositionOpsV2
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x02373c43…3cb3
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x19bcd7e0…ebbc
0x34b655…2a6f
2 touches
0 conflicts
0x31d6dfdf…79cd
0x34b655…2a6f
2 touches
0 conflicts
0x3af9724f…5e27
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:
0xf5b5f7f8…a36d70
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity