pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,759,978
← previous block
next block →
recent activity
Analyzing
Block #83,759,978
10 transactions · 9 stateful · 2026-06-26 06:13:34 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,759,978
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5339c59f
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
· blocks 1
#4
0x5a5d9a99
#6
forward
#7
0x6a3e1905
· blocks 1
#8
setData
#5
0x0f6795d9
#9
0x6a3e1905
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe75cebb6…6b36
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x18ab80cb…19b9
0x34b655…2a6f
2 touches
0 conflicts
0x1b5d2e60…99b5
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
0x53b4ef2b77…528a05
Audit this contract →
← previous block
·
next block →
recent activity