pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,133,688
← previous block
next block →
recent activity
Analyzing
Block #84,133,688
13 transactions · 11 stateful · 2026-06-27 23:44:49 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,133,688
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x1a945f9c
#4
0x98717539
#5
0xed82b078
#6
execFwdPositionOps
· blocks 1
#7
0x6a4060e9
#8
setData
#10
execOrders
#11
execOrders
#12
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac79c76…c4a9
0x34b655…2a6f
4 touches
1 conflict
0x2e6d5c4c…485b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x4b948558…cef3
0x1efe02…37d6
2 touches
0 conflicts
0x52a508f1…2e8a
0x1efe02…37d6
2 touches
0 conflicts
0x90ecce76…8a38
0x1efe02…37d6
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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
0x9ac79c76e2…88c4a9
Audit this contract →
← previous block
·
next block →
recent activity