pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,638,135
← previous block
next block →
recent activity
Analyzing
Block #74,638,135
10 transactions · 8 stateful · 2026-05-14 23:51:35 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,638,135
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6df9e92b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
#5
setData
#6
0x6e49d3…28f8
#7
0xf4a962…bf88
#8
0x39435dac
#9
0x39435dac
#2
0x6df9e92b
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
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0x00000000…0001
0x776059…1d8d
4 touches
1 conflict
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
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:
0x3bd359c1…15433a
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity