pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,284,963
← previous block
next block →
recent activity
Analyzing
Block #90,284,963
12 transactions · 12 stateful · 2026-07-25 19:25:54 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,284,963
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a650e39
#2
updatePrices
#3
0x5a5d9a99
#4
executeBatch
· blocks 1
#6
0x3f5c179b
#7
execFwdPositionOps
· blocks 1
#9
execOrders
#10
setData
#11
execOrders
#5
executeBatch
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9278ea4…99f8
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xb50c9bed…4568
0xe52b14…7230
3 touches
1 conflict
0x76d36e11…fde2
0x34b655…2a6f
2 touches
0 conflicts
0x8de38574…ad6e
0x34b655…2a6f
2 touches
0 conflicts
0xb678410a…0edb
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0002
0x48cba2…b48b
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
1 conflict on slot
0xb9278ea498…aa99f8
Audit this contract →
← previous block
·
next block →
recent activity