pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,990,011
← previous block
next block →
recent activity
Analyzing
Block #90,990,011
7 transactions · 7 stateful · 2026-07-28 06:46:50 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,990,011
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#5
deployWithFactory
#6
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c2d8041…45fd
0x34b655…2a6f
4 touches
1 conflict
0x7ce5b49a…237c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0c58a4e0…2650
0x34b655…2a6f
2 touches
0 conflicts
0x11f14943…6983
0x34b655…2a6f
2 touches
0 conflicts
0x282e68b5…bbd2
0x34b655…2a6f
2 touches
0 conflicts
0x295faadc…ed75
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
0x4c2d8041f4…8b45fd
Audit this contract →
← previous block
·
next block →
recent activity