pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,176,555
← previous block
next block →
recent activity
Analyzing
Block #84,176,555
9 transactions · 8 stateful · 2026-06-28 04:29:55 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,176,555
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
0x0f6795d9
#5
transferWithAuthorization
· blocks 2
#8
setData
#6
transferWithAuthorization
· blocks 1
#7
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9593682…3806
0x754704…b603
6 touches
3 conflicts
0xd0031975…cbe2
0x754704…b603
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x55384053…4a1f
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)
3 conflicts on slot
0xb9593682d5…7c3806
Audit this contract →
← previous block
·
next block →
recent activity