pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,525,616
← previous block
next block →
recent activity
Analyzing
Block #84,525,616
7 transactions · 6 stateful · 2026-06-29 19:16:32 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,525,616
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#4
setData
#6
0xc7e3ec2c
#3
0x0f6795d9
· blocks 1
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x409f20a7…11d1
0x34b655…2a6f
2 touches
0 conflicts
0x4e862605…edc4
0x34b655…2a6f
2 touches
0 conflicts
0x5d521014…b0d3
0x34b655…2a6f
2 touches
0 conflicts
0x74084b4f…eb7c
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
0x0950060282…6794ea
Audit this contract →
← previous block
·
next block →
recent activity