pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,306,829
← previous block
next block →
recent activity
Analyzing
Block #74,306,829
5 transactions · 4 stateful · 2026-05-13 10:58:48 UTC
Parallelism
60
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,306,829
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setData
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda126ddd…b188
0x7b2728…7777
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xe4b00f4b…34c0
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x3e1523…94aa
2 touches
0 conflicts
0x00000000…0002
0x3e1523…94aa
2 touches
0 conflicts
0x00000000…0003
0x3e1523…94aa
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:
0x7b2728c0…a97777
1 conflict on slot
0xda126ddd67…beb188
Audit this contract →
← previous block
·
next block →
recent activity
Feature requests
→