pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,601,978
← previous block
next block →
recent activity
Analyzing
Block #92,601,978
10 transactions · 9 stateful · 2026-08-02 21:58:27 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,601,978
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#2
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#7
setData
#8
execOrders
#9
0x59558d29
#3
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x71cc73a0…d523
0x34b655…2a6f
4 touches
1 conflict
0xda5977c4…2b61
0x34b655…2a6f
4 touches
1 conflict
0x6a95ba16…0c9e
0x34b655…2a6f
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0x0bddd866…4cf7
0x34b655…2a6f
2 touches
0 conflicts
0x0c478a49…ed73
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity