pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,617,619
← previous block
next block →
recent activity
Analyzing
Block #84,617,619
12 transactions · 8 stateful · 2026-06-30 05:30:17 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,617,619
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39435dac
· blocks 1
#3
setData
#4
0x6a4354e1
#5
0x0f6795d9
#6
forward
#7
0x39435dac
#8
0xc4699b…d389
#9
0xd5be30…3b8b
#10
0x98134f…43c5
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x22cd3f83…a62c
0x34b655…2a6f
2 touches
0 conflicts
0x2c30632c…44f3
0x34b655…2a6f
2 touches
0 conflicts
0x3149127f…19a9
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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
0x159b8597f3…8f48a4
Audit this contract →
← previous block
·
next block →
recent activity