pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,234,374
← previous block
next block →
recent activity
Analyzing
Block #90,234,374
8 transactions · 7 stateful · 2026-07-25 15:10:26 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,234,374
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 2
#2
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
setData
#7
execOrders
#3
execFwdPositionOps
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b61477…ed3e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xeee1aff2…184d
0x34b655…2a6f
4 touches
1 conflict
0x3221260e…5b80
0x34b655…2a6f
2 touches
0 conflicts
0x37c70870…b872
0x34b655…2a6f
2 touches
0 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
3 conflicts on slot
0xb6b61477bc…8aed3e
Audit this contract →
← previous block
·
next block →
recent activity