pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,062,483
← previous block
next block →
recent activity
Analyzing
Block #76,062,483
10 transactions · 8 stateful · 2026-05-21 14:26:13 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,062,483
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
forward
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#9
0x42dd8743
#5
multicall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0xd57e82…8ed4
4 touches
1 conflict
0x00000000…0001
0xd57e82…8ed4
4 touches
1 conflict
0x00000000…0003
0xd57e82…8ed4
4 touches
1 conflict
0x5180f24b…0b96
0xd10cf1…7777
4 touches
1 conflict
0x6ac11407…0bcc
0x3bd359…433a
4 touches
1 conflict
0x3d34f2bd…5d63
0x34b655…2a6f
2 touches
0 conflicts
0x4a8069e8…67cc
0x34b655…2a6f
2 touches
0 conflicts
0x676f9f01…a8ac
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:
0xd57e82e3…5d8ed4
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity