pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,240,132
← previous block
next block →
recent activity
Analyzing
Block #76,240,132
13 transactions · 10 stateful · 2026-05-22 10:09:47 UTC
Parallelism
69
/100
Blocked
30
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,240,132
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 3
#2
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
0x0f6795d9
#10
0x0c7abd22
#11
setData
#12
0x39435dac
#3
updatePrices
· blocks 2
#4
updatePrices
· blocks 1
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
2 touches
0 conflicts
0x1be8019f…b769
0x34b655…2a6f
2 touches
0 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
2 touches
0 conflicts
0x28e82642…efa7
0x34b655…2a6f
2 touches
0 conflicts
0x301e1c77…9e30
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:
0xab35264b…1cfa38
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity