pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,465,490
← previous block
next block →
recent activity
Analyzing
Block #76,465,490
10 transactions · 7 stateful · 2026-05-23 11:10:04 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,465,490
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0x98717539
· blocks 1
#3
deposit
#4
0x0f6795d9
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0xd87e25b7…aefc
0x34b655…2a6f
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0003
0x0c65a0…0852
2 touches
0 conflicts
0x1ed86c22…b569
0x0c65a0…0852
2 touches
0 conflicts
0x52c63247…ce02
0x0c65a0…0852
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
0x7cbd466f36…791700
Audit this contract →
← previous block
·
next block →
recent activity