pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,990,000
← previous block
next block →
recent activity
Analyzing
Block #75,990,000
10 transactions · 9 stateful · 2026-05-21 06:23:19 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,990,000
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
execPerpOps
· blocks 1
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
updateTemporalNumericValuesV1
#8
setAddressWhitelisted
#9
setData
#3
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x9bad8822…a28c
0x0555e3…2b9c
2 touches
0 conflicts
0xe64f78af…51a7
0x0555e3…2b9c
2 touches
0 conflicts
0x27409bd7…b5b5
0x065c9d…c394
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
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
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity