pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,096,591
← previous block
next block →
recent activity
Analyzing
Block #75,096,591
8 transactions · 6 stateful · 2026-05-17 02:52:59 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,096,591
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0xb264ae19
#4
0x6a092e03
#6
updateDataFeedsValuesPartial
#7
setData
#2
0x0c7abd22
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x70737748…1bba
0x065c9d…c394
4 touches
1 conflict
0x8f467a46…7b4c
0x065c9d…c394
4 touches
1 conflict
0x33ba9a48…fd4e
0xd32edf…ff58
3 touches
1 conflict
0xce112cd7…1263
0x065c9d…c394
2 touches
0 conflicts
0xd06f0115…dd75
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity