pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,621,849
← previous block
next block →
recent activity
Analyzing
Block #86,621,849
10 transactions · 8 stateful · 2026-07-09 12:19:41 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
#86,621,849
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#7
setData
#8
0x064fdd…b66e
#9
0x39435dac
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb43dc900…22f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x082c81fc…79ff
0x1efe02…37d6
2 touches
0 conflicts
0xb7cbb23c…9a52
0x1efe02…37d6
2 touches
0 conflicts
0xce5ba70b…565a
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0xb43dc90092…2422f2
Audit this contract →
← previous block
·
next block →
recent activity