pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,035,295
← previous block
next block →
recent activity
Analyzing
Block #84,035,295
10 transactions · 8 stateful · 2026-06-27 12:49:13 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,035,295
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0xed82b078
#6
transfer
· blocks 1
#8
setData
#9
0xc7e3ec2c
#4
0x0f6795d9
#7
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0x40040366…0faf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb7027988…888c
0x065c9d…c394
2 touches
0 conflicts
0xd15f66b4…5c6d
0x065c9d…c394
2 touches
0 conflicts
0x22e0cc1d…ad0d
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:
Perpl
1 conflict on slot
0x90a9e3f873…9117ab
Audit this contract →
← previous block
·
next block →
recent activity