pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,731,859
← previous block
next block →
recent activity
Analyzing
Block #75,731,859
10 transactions · 8 stateful · 2026-05-20 01:42:57 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,731,859
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x6a0d1219
· blocks 1
#4
0xed82b078
· blocks 1
#5
0x62be7533
#6
updateDataFeedsValuesPartial
#8
forward
#9
setData
#3
0x6a0d1219
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xdf8ad501…0297
0x065c9d…c394
3 touches
1 conflict
0x8e332e50…ff48
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x298cf0fc…08d8
0x065c9d…c394
2 touches
0 conflicts
0x4082a216…2351
0x065c9d…c394
2 touches
0 conflicts
0x5774de19…e08e
0x065c9d…c394
2 touches
0 conflicts
0x60e17108…96da
0x065c9d…c394
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity