pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,135,980
← previous block
next block →
recent activity
Analyzing
Block #84,135,980
12 transactions · 10 stateful · 2026-06-28 00:00:01 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,135,980
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
multicall
#5
0xed82b078
#6
0xed82b078
#7
0x6a406479
#8
setData
#9
compound
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd08b8a31…0998
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0dec90b6…fbb6
0x0728ed…64cb
2 touches
0 conflicts
0x0dec90b6…fbb7
0x0728ed…64cb
2 touches
0 conflicts
0x1f9642a7…b90c
0x0728ed…64cb
2 touches
0 conflicts
0x1f9642a7…b90d
0x0728ed…64cb
2 touches
0 conflicts
0x2eff2d00…cf0b
0x0728ed…64cb
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
0xd08b8a315e…ef0998
Audit this contract →
← previous block
·
next block →
recent activity