pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,159,628
← previous block
next block →
recent activity
Analyzing
Block #76,159,628
13 transactions · 12 stateful · 2026-05-22 01:13:38 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,159,628
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
0x98717539
#5
0x0c7abd22
#6
updateDataFeedsValuesPartial
#7
forward
#8
0xa391f92f
#9
forward
#10
execute
#11
setData
#12
0x39435dac
#2
0x5339c59f
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4091a82f…a1c6
0x065c9d…c394
2 touches
0 conflicts
0x72537990…d3dc
0x065c9d…c394
2 touches
0 conflicts
0xa69c6cba…6422
0x065c9d…c394
2 touches
0 conflicts
0xcf912747…4d36
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity