pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,949,402
← previous block
next block →
recent activity
Analyzing
Block #75,949,402
10 transactions · 6 stateful · 2026-05-21 01:52:53 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,949,402
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0x5bf9264c
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0xa0c6b3…dafc
#8
0x3057c7…7e89
#9
0x39435dac
#4
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x08d31c28…d50f
0x34b655…2a6f
2 touches
0 conflicts
0x30c10c87…22ec
0x34b655…2a6f
2 touches
0 conflicts
0x4546ebad…b908
0x34b655…2a6f
2 touches
0 conflicts
0x4a8069e8…67cc
0x34b655…2a6f
2 touches
0 conflicts
0x55836904…a6fe
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
0x22e0cc1d4a…90ad04
Audit this contract →
← previous block
·
next block →
recent activity