pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#77,504,435
← previous block
next block →
recent activity
Analyzing
Block #77,504,435
10 transactions · 8 stateful · 2026-05-28 06:31:44 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#77,504,435
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x719d975a
· blocks 1
#2
0x5339c59f
#3
0x5339c59f
#5
artefact_keep
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a17e1c8
#9
setData
#4
0x6c05cd2b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cb16a34…2e1c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x3f51f6…80d5
4 touches
1 conflict
0x00000000…0003
0x3f51f6…80d5
4 touches
1 conflict
0x0c9c83b1…b8b9
0xbc51ff…0f54
4 touches
1 conflict
0xb02cdac2…cf11
0xbc51ff…0f54
4 touches
1 conflict
0x0c9c83b1…b8b9
0xd03f87…7691
4 touches
1 conflict
0x00000000…0004
0x3f51f6…80d5
4 touches
1 conflict
0x00000000…0000
0xf5628e…e591
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
0x6cb16a34d2…262e1c
Audit this contract →
← previous block
·
next block →
recent activity