pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,044,952
← previous block
next block →
recent activity
Analyzing
Block #90,044,952
8 transactions · 7 stateful · 2026-07-24 23:12:45 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,044,952
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#6
setData
#7
execOrders
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x296231a8…d4f4
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af1
0x34b655…2a6f
2 touches
0 conflicts
0x41dc2b7f…1af2
0x34b655…2a6f
2 touches
0 conflicts
0x5f188956…44a6
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:
Perpl
1 conflict on slot
0x6f132c01d5…7dcdcd
Audit this contract →
← previous block
·
next block →
recent activity