pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,194,680
← previous block
next block →
recent activity
Analyzing
Block #83,194,680
10 transactions · 6 stateful · 2026-06-23 15:19:34 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,194,680
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a3aa47e
#9
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xee28d8b5…bd37
0x34b655…2a6f
4 touches
1 conflict
0xac0f2a19…d2e0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x1f078043…1b0f
0x34b655…2a6f
3 touches
1 conflict
0x123338be…73aa
0x34b655…2a6f
3 touches
1 conflict
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
0x793aa64d0d…fdb09c
Audit this contract →
← previous block
·
next block →
recent activity