pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,159,233
← previous block
next block →
recent activity
Analyzing
Block #82,159,233
12 transactions · 10 stateful · 2026-06-18 20:02:09 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,159,233
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
forward
#4
0x0f6795d9
#5
0x6a344f39
#6
setData
#7
0x0e8d07…96bd
#8
0x39435dac
· blocks 1
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49d02518…ca01
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x24b8be…7f9e
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x115995ab…441f
0x34b655…2a6f
2 touches
0 conflicts
0x1630ed91…9774
0x34b655…2a6f
2 touches
0 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
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
0x49d02518bb…c7ca01
Audit this contract →
← previous block
·
next block →
recent activity