pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,263,201
← previous block
next block →
recent activity
Analyzing
Block #76,263,201
13 transactions · 11 stateful · 2026-05-22 12:43:13 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,263,201
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0xed82b078
#3
updatePrices
· blocks 1
#5
updatePrices
#6
deploy
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xed82b078
#10
forward
#11
0x39435dac
· blocks 1
#4
updatePrices
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd784183…67bb
0x34b655…2a6f
4 touches
1 conflict
0xffedeacf…01f1
0x34b655…2a6f
4 touches
1 conflict
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x67d846dd…358c
0x3ecdfa…7777
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
0xfd784183e1…ab67bb
Audit this contract →
← previous block
·
next block →
recent activity