pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,835,278
← previous block
next block →
recent activity
Analyzing
Block #90,835,278
11 transactions · 10 stateful · 2026-07-27 17:48:21 UTC
Parallelism
82
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,835,278
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
· blocks 1
#6
0x29eed2d3
· blocks 1
#9
setData
#10
execOrders
#5
batchUpdate
#7
0x29eed2d3
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x449d101e…ea3f
0xa6afd3…d132
4 touches
1 conflict
0x00abac72…c0c9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x7d653dc5…3fe5
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x449d101e22…62ea3f
Audit this contract →
← previous block
·
next block →
recent activity