pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,456,710
← previous block
next block →
recent activity
Analyzing
Block #90,456,710
11 transactions · 10 stateful · 2026-07-26 10:03:47 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,456,710
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
0x3f5c179b
#7
0xc5a04723
#8
forward
#9
0x6a65dbfb
#10
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf346808d…6ad4
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaee74ef4…60d5
0x34b655…2a6f
4 touches
1 conflict
0xbaf2476c…859d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xf0783775…7b62
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
0xf346808d47…866ad4
Audit this contract →
← previous block
·
next block →
recent activity