pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,643,396
← previous block
next block →
recent activity
Analyzing
Block #90,643,396
7 transactions · 5 stateful · 2026-07-27 01:42:56 UTC
Parallelism
71
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,643,396
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#6
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0x9716ecca…aa30
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x0406a8bb…39a9
0x34b655…2a6f
2 touches
0 conflicts
0x046e4d12…847a
0x34b655…2a6f
2 touches
0 conflicts
0x051e1801…1126
0x34b655…2a6f
2 touches
0 conflicts
0x0d7b3beb…b1fa
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
0xb5f244d5d7…d9f550
Audit this contract →
← previous block
·
next block →
recent activity