pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,254,952
← previous block
next block →
recent activity
Analyzing
Block #75,254,952
8 transactions · 6 stateful · 2026-05-17 20:30:17 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,254,952
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePosition
#3
0x5de3085d
#4
0xed82b078
#5
setData
#6
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x0bfe4e7a…805c
0x6657d1…8ccc
2 touches
0 conflicts
0x0e273f63…ef1d
0x6657d1…8ccc
2 touches
0 conflicts
0x2a52178e…cdd0
0x6657d1…8ccc
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
0x8a85cf3dc8…792868
Audit this contract →
← previous block
·
next block →
recent activity