pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,080,309
← previous block
next block →
recent activity
Analyzing
Block #92,080,309
9 transactions · 7 stateful · 2026-08-01 02:14:50 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,080,309
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
resolve
#6
execOrders
#7
execOrders
#8
setData
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd793c15e…7dba
0x34b655…2a6f
4 touches
1 conflict
0x61e273d4…7a19
0x34b655…2a6f
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x1c3659d8…3efc
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x34ad8216…1400
0x34b655…2a6f
2 touches
0 conflicts
0x35a9f06c…7689
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
0xd793c15e21…747dba
Audit this contract →
← previous block
·
next block →
recent activity