pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,619,455
← previous block
next block →
recent activity
Analyzing
Block #84,619,455
13 transactions · 10 stateful · 2026-06-30 05:42:27 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,619,455
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setAccess
#2
multicall
#3
updateDataFeedsValuesPartial
#4
forward
#5
0x0f6795d9
#6
forward
#7
0xed82b078
· blocks 1
#9
0x6a4357bb
#10
setData
#11
0x32366535
#12
0xcfb6c4…dd78
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc14e8f20…1d80
0x40c49f…2af0
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x793aa64d…b09c
0x34b655…2a6f
2 touches
0 conflicts
0x793aa64d…b09d
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:
0x40c49f17…d22af0
1 conflict on slot
0xc14e8f205f…b21d80
Audit this contract →
← previous block
·
next block →
recent activity