pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,230,122
← previous block
next block →
recent activity
Analyzing
Block #76,230,122
12 transactions · 9 stateful · 2026-05-22 09:03:08 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,230,122
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updatePrices
· blocks 3
#5
updateDataFeedsValuesPartial
#6
setData
#7
spin
#8
0xe4deca…0820
#9
0x2e4abb…e57a
#10
0x785f5745
#11
0x39435dac
#2
updatePrices
· blocks 2
#3
updatePrices
· blocks 1
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
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
0x0fe4cf83…9349
0x0c65a0…0852
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xb6ea5284…af71
0x1308d7…ff6c
2 touches
0 conflicts
0xf5c85b15…ce74
0x1308d7…ff6c
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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