pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,659,905
← previous block
next block →
recent activity
Analyzing
Block #83,659,905
12 transactions · 12 stateful · 2026-06-25 19:05:58 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,659,905
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x39435dac
#4
0x6a3d7c8e
#5
callDiamondWithEIP2612Signature
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x0f6795d9
#10
setData
#11
0x39435dac
#2
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xf19225e1…bf10
0x40c49f…2af0
3 touches
1 conflict
0x7baef344…c15c
0x40c49f…2af0
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
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:
0x40c49f17…d22af0
1 conflict on slot
0xa9db7b4dd0…562957
Audit this contract →
← previous block
·
next block →
recent activity