pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,063,732
← previous block
next block →
recent activity
Analyzing
Block #100,063,732
11 transactions · 11 stateful · 2026-08-29 02:21:11 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,063,732
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0x6ad2e98b
#3
0xab083028
#4
0x59558d29
#5
updateDataFeedsValuesPartial
#6
execOrders
· blocks 2
#9
execFwdPositionOpsV2
#10
0x6a92428f
#7
execOrders
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98c943e…7c44
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x49f39582…ccc7
0x754704…b603
2 touches
0 conflicts
0x53e67340…60f7
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:
Perpl
3 conflicts on slot
0xf98c943e1d…327c44
Audit this contract →
← previous block
·
next block →
recent activity