pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,130,775
← previous block
next block →
recent activity
Analyzing
Block #84,130,775
11 transactions · 7 stateful · 2026-06-27 23:25:23 UTC
Parallelism
82
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,130,775
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
0x0f6795d9
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#10
setData
#3
updatePrices
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x99910689…8959
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x185ede13…0a39
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x1d30b594…5823
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:
0xd637b38f…c64160
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity