pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,963,485
← previous block
next block →
recent activity
Analyzing
Block #85,963,485
11 transactions · 10 stateful · 2026-07-06 11:00:41 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,963,485
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
updatePrices
#3
0x0f6795d9
#4
0x0f6795d9
#5
permit2TransferAndMulticall
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x6a4b8b51
#9
setData
#10
0x39435dac
#6
permit2TransferAndMulticall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x489fcaf8…568d
0xd5d960…eaee
4 touches
1 conflict
0x2b48a867…0578
0xbeef06…b8f5
4 touches
1 conflict
0x9d266cee…2f00
0xbeef06…b8f5
4 touches
1 conflict
0xd942172e…5811
0xbeef06…b8f5
4 touches
1 conflict
0x1740a069…8c8a
0xd5d960…eaee
4 touches
1 conflict
0x00000000…0002
0x1c8a33…d316
4 touches
1 conflict
0xa207048b…6a7e
0x5a66a5…cba8
4 touches
1 conflict
0x00000000…0003
0x98a45d…206a
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:
0xd5d960e8…a1eaee
1 conflict on slot
0x489fcaf8fc…e7568d
Audit this contract →
← previous block
·
next block →
recent activity