pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,623,504
← previous block
next block →
recent activity
Analyzing
Block #84,623,504
10 transactions · 8 stateful · 2026-06-30 06:09:18 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,623,504
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x39435dac
· blocks 2
#6
setData
#7
updatePosition
#8
0x1050d9…c158
#5
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7585925a…3f45
0x34b655…2a6f
6 touches
3 conflicts
0x24227bc5…cb16
0x34b655…2a6f
4 touches
1 conflict
0x27d815d2…5ca9
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x340b6233…0bcc
0x34b655…2a6f
4 touches
1 conflict
0x3d50dc3e…ea0b
0x34b655…2a6f
4 touches
1 conflict
0x469607a6…3940
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
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:
Perpl
3 conflicts on slot
0x7585925ad9…1a3f45
Audit this contract →
← previous block
·
next block →
recent activity