pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,525,093
← previous block
next block →
recent activity
Analyzing
Block #87,525,093
10 transactions · 9 stateful · 2026-07-13 16:59:24 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
#87,525,093
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x957d4ba0
· blocks 2
#4
updatePrices
#5
permit2TransferAndMulticall
#6
updateDataFeedsValuesPartial
#7
updatePriceFeedsIfNecessary
#8
0x0f6795d9
#9
0x39435dac
#2
0x957d4ba0
· blocks 1
#3
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x34443913…cbf3
0x336ed4…c59c
4 touches
1 conflict
0x4a870d86…79ef
0x336ed4…c59c
4 touches
1 conflict
0x006e55b1…660f
0x8d1565…6723
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x20f0fd22…727a
0x09c48a…b00a
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:
0x8d156514…236723
3 conflicts on slot
0x10a2bd5d43…51ad6d
Audit this contract →
← previous block
·
next block →
recent activity