pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,956,192
← previous block
next block →
recent activity
Analyzing
Block #75,956,192
12 transactions · 11 stateful · 2026-05-21 02:38:05 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,956,192
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
relay
#6
0x0f6795d9
· blocks 1
#8
0x5339c59f
#9
setData
#10
0xae5eed…e426
#7
0x5339c59f
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w0
7
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaaa6b43…13ec
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1c97003e…fe67
0x065c9d…c394
3 touches
1 conflict
0xab85d49e…205b
0x065c9d…c394
3 touches
1 conflict
0x2135b454…9a67
0x065c9d…c394
2 touches
0 conflicts
0xafb05410…fbb3
0x065c9d…c394
2 touches
0 conflicts
0xd1394a1f…b33e
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xfaaa6b4335…f113ec
Audit this contract →
← previous block
·
next block →
recent activity