pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,349,349
← previous block
next block →
recent activity
Analyzing
Block #77,349,349
12 transactions · 8 stateful · 2026-05-27 13:18:43 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,349,349
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
0x0c7abd22
#10
setData
#11
0x39435dac
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x3a1479bc…83a2
0x065c9d…c394
2 touches
0 conflicts
0xacb58778…d5a8
0x065c9d…c394
2 touches
0 conflicts
0xb87e2fe2…35a3
0x065c9d…c394
2 touches
0 conflicts
0xcf1b0467…3ed3
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
0xcc8faac238…88c766
Audit this contract →
← previous block
·
next block →
recent activity