pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,345,988
← previous block
next block →
recent activity
Analyzing
Block #77,345,988
8 transactions · 7 stateful · 2026-05-27 12:56:24 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,345,988
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#4
0x0c7abd22
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#2
0xab083028
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x8488f10f…9356
0x69df8a…6292
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0478d776…0770
0x065c9d…c394
4 touches
1 conflict
0x8488f10f…9355
0x69df8a…6292
4 touches
1 conflict
0x8488f10f…9354
0x69df8a…6292
4 touches
1 conflict
0x8488f10f…9353
0x69df8a…6292
4 touches
1 conflict
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: MarginAccount
1 conflict on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity