pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,791,550
← previous block
next block →
recent activity
Analyzing
Block #75,791,550
9 transactions · 3 stateful · 2026-05-20 08:20:00 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,791,550
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98839e…b2af
#3
0x887bc8…072f
#4
setData
#5
0x0bfc17…a622
#6
0x113516…166e
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97d5efed…1aa4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2f7781d6…e632
0x34b655…2a6f
2 touches
0 conflicts
0x4ebc22e7…0702
0x34b655…2a6f
2 touches
0 conflicts
0x537b38ff…2c21
0x34b655…2a6f
2 touches
0 conflicts
0x74e485b1…d380
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x97d5efed7f…b81aa4
Audit this contract →
← previous block
·
next block →
recent activity