pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,290,385
← previous block
next block →
recent activity
Analyzing
Block #91,290,385
10 transactions · 9 stateful · 2026-07-29 07:59:38 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,290,385
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrder
· blocks 1
#4
0x62be7533
#5
updateDataFeedsValuesPartial
#6
batchUpdate
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77a700dc…2f59
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x9c39ade3…860f
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xb65e224b…5698
0x34b655…2a6f
3 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
2 touches
0 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
2 touches
0 conflicts
0xa6b48d6e…0705
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
0x77a700dc61…0c2f59
Audit this contract →
← previous block
·
next block →
recent activity