pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,043,086
← previous block
next block →
recent activity
Analyzing
Block #71,043,086
11 transactions · 9 stateful · 2026-04-28 08:19:40 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,043,086
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
poke
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#7
0x0c7abd22
#8
0x69f06e13
#9
setData
#10
0x39435dac
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d51535…83f7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x88ab4d92…bc2f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2602dc73…8c7c
0x065c9d…c394
4 touches
1 conflict
0x32b84fbe…18d5
0x065c9d…c394
4 touches
1 conflict
0x9496c60e…35e6
0x065c9d…c394
2 touches
1 conflict
0x7cd6df95…1e49
0x065c9d…c394
2 touches
1 conflict
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x38d51535bf…cb83f7
Audit this contract →
← previous block
·
next block →
recent activity