pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,784,523
← previous block
next block →
recent activity
Analyzing
Block #90,784,523
9 transactions · 8 stateful · 2026-07-27 13:32:53 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,784,523
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 2
#4
batchUpdate
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
setData
#3
execFwdPositionOps
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7032dc14…49ea
0x34b655…2a6f
4 touches
1 conflict
0x8dbfdaf6…6925
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xbd97c3fe…85d3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xde9d38a8…4c0f
0x34b655…2a6f
4 touches
1 conflict
0xed568f08…59d8
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
0x7032dc1485…0e49ea
Audit this contract →
← previous block
·
next block →
recent activity