pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,551,043
← previous block
next block →
recent activity
Analyzing
Block #75,551,043
10 transactions · 8 stateful · 2026-05-19 05:36:58 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,551,043
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xff401d8f
#2
updateDataFeedsValuesPartial
#3
0x39435dac
#4
setData
#5
0x62be7533
#6
0x0c7abd22
· blocks 1
#7
updateTemporalNumericValuesV1
#9
0x5d2fd812
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xcc27941f…cbc6
0x065c9d…c394
2 touches
0 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x3d34f2bd…5d63
0x34b655…2a6f
2 touches
0 conflicts
0x537e2e5b…c3ab
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity