pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,184,438
← previous block
next block →
recent activity
Analyzing
Block #77,184,438
13 transactions · 11 stateful · 2026-05-26 18:56:46 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,184,438
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a15ed66
#7
setData
#8
0xed82b078
#9
0x6a15ed65
#10
execOrders
#11
execOrders
#12
execOrders
#6
0xaf47a8bb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12a9b76e…cb76
0x3bd359…433a
4 touches
1 conflict
0x67d846dd…358c
0x825829…7777
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0x8f36eed7…bd8b
0x9f3832…4ae4
4 touches
1 conflict
0xc8bf4f19…1652
0x9f3832…4ae4
4 touches
1 conflict
0xc8bf4f19…1653
0x9f3832…4ae4
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:
Wrapped MON (WMON)
1 conflict on slot
0x12a9b76ee5…a5cb76
Audit this contract →
← previous block
·
next block →
recent activity