pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,157,945
← previous block
next block →
recent activity
Analyzing
Block #76,157,945
13 transactions · 13 stateful · 2026-05-22 01:02:26 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,157,945
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xed82b078
#3
0x5339c59f
· blocks 1
#4
updatePrices
#5
0x6943a490
#6
updateDataFeedsValuesPartial
#8
forward
#9
forward
#10
forward
#11
setData
#12
0x39435dac
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2e49b124…1afb
0x0a4fcb…a602
2 touches
0 conflicts
0x9adf2539…8cce
0x0a4fcb…a602
2 touches
0 conflicts
0x9adf2539…8cd4
0x0a4fcb…a602
2 touches
0 conflicts
0x9adf2539…8cd5
0x0a4fcb…a602
2 touches
0 conflicts
0x9adf2539…8cd6
0x0a4fcb…a602
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