pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,881,008
← previous block
next block →
recent activity
Analyzing
Block #75,881,008
7 transactions · 6 stateful · 2026-05-20 18:17:44 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,881,008
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updateDataFeedsValuesPartial
#3
artefact_keep
#6
setData
#4
0x0c7abd22
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x484140b3…de0f
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x8e1be7cc…3146
0x065c9d…c394
2 touches
0 conflicts
0x986d3d7f…69d9
0x065c9d…c394
2 touches
0 conflicts
0xc95dad03…c098
0x065c9d…c394
2 touches
0 conflicts
0xdf462037…1ea4
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x443a3e479f…3af4a4
Audit this contract →
← previous block
·
next block →
recent activity