pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,543,685
← previous block
next block →
recent activity
Analyzing
Block #85,543,685
9 transactions · 8 stateful · 2026-07-04 12:23:18 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,543,685
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updatePrices
#4
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a48fbae
#7
setData
#2
0xab083028
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x7fe4a652…079b
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3cb231a9…887d
0x34b655…2a6f
4 touches
1 conflict
0x4bd2fdc3…0d6d
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6a9e
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
0x5eb187dd4c…a6b1d6
Audit this contract →
← previous block
·
next block →
recent activity