pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#82,047,775
← previous block
next block →
recent activity
Analyzing
Block #82,047,775
13 transactions · 10 stateful · 2026-06-18 07:38:25 UTC
Parallelism
85
/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,047,775
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
commitVerification
#2
updateDataFeedsValuesPartial
#3
0x39435dac
· blocks 1
#5
forward
#6
setData
#7
executeBatch
#8
forward
#9
forward
#10
0x6a33a0e8
#11
0x1d71fb…c9e0
#12
0x39435dac
#4
0x39435dac
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
0x76aa1f3f…a444
0x34b655…2a6f
4 touches
1 conflict
0x780f643a…9738
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0xf6322736…e546
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 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
0x76aa1f3f1f…3ba444
Audit this contract →
← previous block
·
next block →
recent activity