pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,891,529
← previous block
next block →
recent activity
Analyzing
Block #74,891,529
13 transactions · 9 stateful · 2026-05-16 04:02:54 UTC
Parallelism
85
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,891,529
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a07ece5
#2
0x6a07ece5
#3
updatePrices
· blocks 1
#5
updateDataFeedsValuesPartial
#6
exactInputSingle
#7
0x6a07ece0
#8
exactInputSingle
#9
setData
#10
0x39435dac
· blocks 1
#12
0x053c0052
#4
updatePrices
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0003
0x2d59fc…cd50
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x3f1434d4…1ce1
0x3bd359…433a
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity