pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,194,535
← previous block
next block →
recent activity
Analyzing
Block #82,194,535
12 transactions · 8 stateful · 2026-06-18 23:57:26 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,194,535
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x13572d0b
#2
0xa96df62f
#3
updateDataFeedsValuesPartial
#4
0x62be7533
#5
execOrders
· blocks 1
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
0x6a34865e
#9
setData
#11
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x73f16822…0338
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x52092bea…94fa
0x000000…012a
2 touches
0 conflicts
0x79174f76…a796
0x09c48a…b00a
2 touches
0 conflicts
0xaa0fae2a…6238
0x09c48a…b00a
2 touches
0 conflicts
0xe5fc8127…b644
0x09c48a…b00a
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity