pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,105,679
← previous block
next block →
recent activity
Analyzing
Block #84,105,679
13 transactions · 11 stateful · 2026-06-27 20:38:13 UTC
Parallelism
69
/100
Blocked
27
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,105,679
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#6
0x6a40352d
#7
transfer
· blocks 3
#11
setData
#12
0x39435dac
#8
transfer
· blocks 2
#9
transfer
· blocks 1
#10
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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:
USDC (USDC)
6 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity