pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,518,039
← previous block
next block →
recent activity
Analyzing
Block #85,518,039
11 transactions · 10 stateful · 2026-07-04 09:32:29 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,518,039
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0x6ad2e98b
#3
0xab083028
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#7
0x3f5c179b
#9
setData
#10
0x39435dac
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x665a59a6…79a6
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x63f5c02f…6853
0x3bd359…433a
2 touches
0 conflicts
0x5da3ed7f…34d7
0x46a15b…4364
2 touches
0 conflicts
0x5da3ed7f…34d8
0x46a15b…4364
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
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
0x1bee5aeac8…6f5f61
Audit this contract →
← previous block
·
next block →
recent activity