pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,814,380
← previous block
next block →
recent activity
Analyzing
Block #75,814,380
9 transactions · 8 stateful · 2026-05-20 10:52:05 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,814,380
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x785f5745
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a0d92cd
#6
0xe9316489
· blocks 1
#8
setData
#7
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92a0110c…88c6
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0e1120cd…9b18
0x0c65a0…0852
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x1a44398b…cf39
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x92a0110cab…9188c6
Audit this contract →
← previous block
·
next block →
recent activity