pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,230,862
← previous block
next block →
recent activity
Analyzing
Block #76,230,862
13 transactions · 12 stateful · 2026-05-22 09:08:04 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,230,862
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
· blocks 1
#4
updatePrices
#5
0xed82b078
· blocks 1
#7
0xc5a04723
#8
relay
#9
forward
#10
0xe9316489
#11
setData
#12
0x39435dac
#3
updatePrices
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0x29bc6b8d…bc2d
0x065c9d…c394
2 touches
0 conflicts
0x46c9498e…2f74
0x065c9d…c394
2 touches
0 conflicts
0x479de045…edda
0x065c9d…c394
2 touches
0 conflicts
0x7b8ae145…4cae
0x065c9d…c394
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity