pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,238,263
← previous block
next block →
recent activity
Analyzing
Block #90,238,263
11 transactions · 8 stateful · 2026-07-25 15:30:01 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,238,263
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 1
#3
0x29eed2d3
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a64d6f1
#8
setData
#9
0x876106…f0b3
#10
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6628
0x34b655…2a6f
4 touches
1 conflict
0x0181bb37…6629
0x34b655…2a6f
4 touches
1 conflict
0x345f75e4…71a0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d1c2806…5947
0x34b655…2a6f
4 touches
1 conflict
0x51fa9653…f562
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity