pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,190,105
← previous block
next block →
recent activity
Analyzing
Block #84,190,105
10 transactions · 8 stateful · 2026-06-28 06:00:06 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,190,105
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
#3
0xa96df62f
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5bf9264c
· blocks 1
#8
0x0f6795d9
#9
setData
#7
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ed48a1a…b936
0x065c9d…c394
2 touches
0 conflicts
0x84259a12…9c95
0x065c9d…c394
2 touches
0 conflicts
0x9e762a96…5fb7
0x065c9d…c394
2 touches
0 conflicts
0xad4f9d82…4b98
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0xac2a02739b…817212
Audit this contract →
← previous block
·
next block →
recent activity