pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,336,287
← previous block
next block →
recent activity
Analyzing
Block #75,336,287
13 transactions · 6 stateful · 2026-05-18 05:34:51 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,336,287
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#3
withdraw
#4
updateDataFeedsValuesPartial
#5
0x6a0aa573
#6
0x342db3…eb82
#7
0x718a0b…2fa6
#8
setData
#9
0xd13208…5fe5
#10
0x6a2fa3…4107
#11
0x279634…bacb
#12
0x39435dac
#2
0x98717539
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
0x60f7fbaf…bd58
0x34b655…2a6f
4 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
0x310a7246…2dcb
0x34b655…2a6f
2 touches
0 conflicts
0x37d49489…9309
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x4d7ce95f…ecbd
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity