pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,975,176
← previous block
next block →
recent activity
Analyzing
Block #99,975,176
13 transactions · 13 stateful · 2026-08-28 18:55:20 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,975,176
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
execOrders
#4
0xab083028
· blocks 1
#5
0x59558d29
#6
execOrders
· blocks 1
#8
execFwdPositionOpsV2
#10
0x6a91da10
#11
setData
#12
execOrders
#7
execOrders
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x39126904…24d8
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
0x9ec9f52c…cf48
0x34b655…2a6f
4 touches
1 conflict
0xaef85d8c…963b
0x34b655…2a6f
4 touches
1 conflict
0xc425407b…0ec9
0x34b655…2a6f
4 touches
1 conflict
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
0x42522e76ce…082592
Audit this contract →
← previous block
·
next block →
recent activity