pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,199,521
← previous block
next block →
recent activity
Analyzing
Block #75,199,521
10 transactions · 8 stateful · 2026-05-17 14:20:10 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,199,521
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exec
#2
forward
· blocks 1
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x6a09cf12
#7
setData
#8
0x39435dac
· blocks 1
#3
forward
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x900f68…bff2
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xbc467e7a…af36
0x21e325…7777
2 touches
0 conflicts
0xfedca6d7…b15f
0x21e325…7777
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0xd6aabe89…92f5
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:
Perpl
1 conflict on slot
0x5fad6fee64…277714
Audit this contract →
← previous block
·
next block →
recent activity