pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,704,375
← previous block
next block →
recent activity
Analyzing
Block #71,704,375
8 transactions · 6 stateful · 2026-05-01 09:47:27 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,704,375
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9036287a
· blocks 1
#2
updatePrices
#3
0xeffdedb0
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x1208f34d…b8c0
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x4b95d6ad…1070
0x065c9d…c394
3 touches
1 conflict
0xfd0981fc…47e4
0x065c9d…c394
3 touches
1 conflict
0x508387de…c644
0x2a68ba…90c5
2 touches
0 conflicts
0xd74d5bed…5e7e
0x2a68ba…90c5
2 touches
0 conflicts
0x1a4b4152…0a08
0x33663b…4897
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x47b807a243…c53307
Audit this contract →
← previous block
·
next block →
recent activity