pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,336,006
← previous block
next block →
recent activity
Analyzing
Block #75,336,006
15 transactions · 9 stateful · 2026-05-18 05:33:00 UTC
Parallelism
87
/100
Blocked
11
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,336,006
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
#2
0xab083028
· blocks 1
#3
0x98717539
#4
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a0aa504
#9
0x5c9e3b…1a0f
#10
0x7f71f1…7f4a
#11
0xc9f9a3…4e51
#12
0x487473…fe61
#13
setData
#14
withdraw
#5
0x23afbff3
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35e5bfb4…172c
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0001
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0002
0x059114…ac3b
2 touches
0 conflicts
0x00000000…0003
0x059114…ac3b
2 touches
0 conflicts
0x12ba54c9…b729
0x059114…ac3b
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x35e5bfb477…69172c
Audit this contract →
← previous block
·
next block →
recent activity