pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,479,082
← previous block
next block →
recent activity
Analyzing
Block #75,479,082
12 transactions · 7 stateful · 2026-05-18 21:28:55 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,479,082
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
· blocks 1
#2
0x5bf9264c
#3
0x5bf9264c
#4
receiveMessage
#5
0x6a0b850f
#7
updateDataFeedsValuesPartial
#8
0x044ea300
#9
setData
#10
0x024e6900
#11
0x034e3a00
#6
permit2TransferAndMulticall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x094452…0a09
4 touches
1 conflict
0x9e223b01…38b2
0x3bd359…433a
4 touches
1 conflict
0x62e20208…be65
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x00000000…0000
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…0001
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000c
0x2b37ef…0bdc
2 touches
0 conflicts
0x00000000…000f
0x2b37ef…0bdc
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:
0x0944526d…170a09
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity