pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,700,398
← previous block
next block →
recent activity
Analyzing
Block #75,700,398
10 transactions · 8 stateful · 2026-05-19 22:13:24 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,700,398
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
approve
#3
0x0f6795d9
#4
0x0f6795d9
#5
updatePosition
#6
0xce1e7030
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x42845a1c…145b
0x34b655…2a6f
2 touches
0 conflicts
0x42845a1c…145c
0x34b655…2a6f
2 touches
0 conflicts
0x4b347984…9255
0x34b655…2a6f
2 touches
0 conflicts
0x69941f7e…3b1d
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
0xa998841984…609f45
Audit this contract →
← previous block
·
next block →
recent activity