pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,612,353
← previous block
next block →
recent activity
Analyzing
Block #87,612,353
9 transactions · 8 stateful · 2026-07-14 02:43:05 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,612,353
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
permit2TransferAndMulticall
· blocks 1
#3
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#4
permit2TransferAndMulticall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb02d03d…5383
0xaca92e…35da
4 touches
1 conflict
0xaeb46f64…7cfc
0xaca92e…35da
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1f3b2a39…ab2c
0x09475a…400f
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xa207048b…6a7e
0x5a66a5…cba8
2 touches
0 conflicts
0x00000000…0003
0x98a45d…206a
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:
0xaca92e43…2435da
1 conflict on slot
0xbb02d03d67…ec5383
Audit this contract →
← previous block
·
next block →
recent activity