pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,048,174
← previous block
next block →
recent activity
Analyzing
Block #86,048,174
9 transactions · 8 stateful · 2026-07-06 20:26:27 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,048,174
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
0x234623f7
· blocks 1
#3
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#8
0xc7e3ec2c
#4
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc984b78b…503a
0x62ab75…c800
4 touches
1 conflict
0x00000000…0005
0x62ab75…c800
4 touches
1 conflict
0x73cb5554…4902
0x754704…b603
4 touches
1 conflict
0xc984b78b…5036
0x62ab75…c800
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
2 touches
0 conflicts
0xaa226690…99ba
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6425
0x34b655…2a6f
2 touches
0 conflicts
0xd35315c0…5422
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:
0x62ab757c…36c800
1 conflict on slot
0xc984b78b7c…4d503a
Audit this contract →
← previous block
·
next block →
recent activity