pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,141,080
← previous block
next block →
recent activity
Analyzing
Block #76,141,080
10 transactions · 9 stateful · 2026-05-21 23:09:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,141,080
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
· blocks 1
#5
0x0f6795d9
#6
updatePriceFeedsIfNecessary
#7
0x0f6795d9
#8
setData
#9
0x39435dac
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x03622417…0bd6
0x2880ab…7b43
2 touches
0 conflicts
0x03622417…0bd7
0x2880ab…7b43
2 touches
0 conflicts
0x05e5ce66…b69d
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
2 touches
0 conflicts
0x1df0c798…adbb
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity