pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,571,850
← previous block
next block →
recent activity
Analyzing
Block #83,571,850
10 transactions · 9 stateful · 2026-06-25 09:18:04 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,571,850
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x40e79b1b
· blocks 2
#5
setData
#6
0x9e76c652
#7
forward
#8
0x6a3cf2c4
#9
0xe9316489
#3
0x23afbff3
· blocks 1
#4
0x40e79b1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40c9380a…2115
0xa6afd3…d132
6 touches
3 conflicts
0x4cd6928f…1a19
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x05b8ccbb…46bc
0x2ab50b…5c41
2 touches
0 conflicts
0x100cf374…6949
0x2ab50b…5c41
2 touches
0 conflicts
0x1063339b…b9a3
0x2ab50b…5c41
2 touches
0 conflicts
0x25d518a7…3c48
0x2ab50b…5c41
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
3 conflicts on slot
0x40c9380a4e…002115
Audit this contract →
← previous block
·
next block →
recent activity