pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,066,757
← previous block
next block →
recent activity
Analyzing
Block #75,066,757
8 transactions · 6 stateful · 2026-05-16 23:33:41 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,066,757
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x6a08ff4c
#5
setData
#6
0x39435dac
#7
0x39435dac
#2
0x5bf9264c
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
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x81e1f4e8…08d7
0x34b655…2a6f
2 touches
0 conflicts
0x96aa7e47…f584
0x34b655…2a6f
2 touches
0 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
2 touches
0 conflicts
0xc108f63d…204f
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
0xac2a02739b…817212
Audit this contract →
← previous block
·
next block →
recent activity